Skip to content
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.

deprecation: Don't show errors on imports and exports #3141

Merged
merged 2 commits into from
Aug 18, 2017
Merged

deprecation: Don't show errors on imports and exports #3141

merged 2 commits into from
Aug 18, 2017

Conversation

ajafff
Copy link
Contributor

@ajafff ajafff commented Aug 18, 2017

PR checklist

  • Addresses an existing issue: #0000
  • New feature, bugfix, or enhancement
    • Includes tests
  • Documentation update

Overview of change:

Imports and exports don't do any harm. We now only show errors at deprecated usage to correctly handle deprecated overload signatures. So this is basically a followup on #2883.

Is there anything you'd like reviewers to focus on?

CHANGELOG.md entry:

[bugfix] deprecation no longer shows errors on imports and exports

Imports don't do any harm. We now only show errors at deprecated usage to account for deprecated overload signatures.

[bugfix] `deprecation` no longer shows errors on imports
Copy link
Contributor

@adidahiya adidahiya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this makes sense; the deprecated symbols should only produce warnings at their usage sites, and this rule shouldn't care about "no-unused-variable" type concerns.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants