Skip to content

Too many deprecation indications #146

@gugrim

Description

@gugrim

In an import statement, functions are indicated as deprecated if any overloaded function is annotated as @deprecated. In the below example, "mergeMap" is overstricken because there are deprecated overloads of mergeMap, but not all:

import {filter, map, mergeMap} from "rxjs/operators";

The same happens with function calls. In the below example, "subscribe" is overstricken because there are deprecated overloads, but the one I use is not deprecated:

this.doi.auth.authenticatedState().subscribe(loggedIn => this.authenticatedStateChanged(loggedIn));

In the import case, I would prefer if imported functions are overstricken only if all overloads are deprecated.

In the invocation case, it should be overstricken only if the invoked function is deprecated. If that is difficult to achieve, it would be better if it is overstricken only if all overloads are deprecated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions