Deprecate {{exception}} macro #6163
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
caugner
approved these changes
May 4, 2022
OnkarRuikar
pushed a commit
to OnkarRuikar/yari
that referenced
this pull request
Jun 2, 2022
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In mdn/content#15677, I removed the last occurrences of the
{{exception}}macro.In order to be sure this macro doesn't sneak back in
mdn/contentwhile it gets removed frommdn/translated-content, we want aMacroDeprecationErrorflaw to be raised if a page is committed again with this macro.This flaw can be noticed by the committer, the reviewer, and, via the flaw dashboard, all
mdn/contentowners. (Given we normally have 0 such flaws, it will be very noticeable)