Fix deprecation ID displays in JS mode #2483
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
In the pure JS release, these weren't working because the Dart-to-JS logger didn't know to pass along the deprecation metadata when falling back to the wrapped StderrLogger. In the embedded release, these weren't working because we didn't give it an update to match the stderr logger.
jathak
approved these changes
Jan 13, 2025
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 the pure JS release, these weren't working because the Dart-to-JS
logger didn't know to pass along the deprecation metadata when falling
back to the wrapped StderrLogger. In the embedded release, these
weren't working because we didn't give it an update to match the
stderr logger.