[BUGFIX] properly surface deprecation message #1562
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
I think wrapping these in LOCAL_DEBUG ends up causing these to not actually be seen by anyone. It's also unnecessary, `deprecate` should already be pluggable/strippable in Ember, but it probably doesn't matter in this case anyway, because most of the time the compiler isn't shipped to the browser anyway and should be (???) running in dev mode by default? I hope? Anyway if that last part isn't true and these still aren't being seen, then it would be something to fix in Ember.
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.
I think wrapping these in LOCAL_DEBUG ends up causing these to not actually be seen by anyone. It's also unnecessary,
deprecateshould already be pluggable/strippable in Ember, but it probably doesn't matter in this case anyway, because most of the time the compiler isn't shipped to the browser anyway and should be (???) running in dev mode by default? I hope?Anyway if that last part isn't true and these still aren't being seen, then it would be something to fix in Ember.