Skip to content

build(dgeni): do not warn if @breaking-change is used without @deprecated #12750

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

devversion
Copy link
Member

  • Similarly to the TSLint rule, we should only warn (on gulp docs) if there is a @deprecated tag without a @breaking-change tag. If there is a @breaking-change tag, but no @deprecated tag, it's valid because a breaking change does not always involve a deprecation (e.g. "to be made required").
  • Updates the log patching for the Dgeni package to also hide warnings for mixins that don't end with MixinBase.

…ated

* Similarly as the TSLint rule, we should only warn (on `gulp docs`) if there is a `@deprecated` tag without a `@breaking-change` tag. If there is a `@breaking-change` tag, but no `@deprecated` tag, it's valid because a breaking change does not always involve a deprecation (e.g. "to be made required").
* Updates the log patching for the Dgeni package to also hide warnings for mixins that don't end with `MixinBase`.
@devversion devversion requested a review from jelbourn as a code owner August 20, 2018 10:28
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 20, 2018
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Aug 20, 2018
@jelbourn jelbourn merged commit 7d140a2 into angular:master Aug 20, 2018
@devversion devversion deleted the build/dgeni-breaking-change-deprecated branch August 20, 2018 20:39
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants