-
Notifications
You must be signed in to change notification settings - Fork 286
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
Problems with ember-cli-deprecation-workflow #857
Comments
This interaction isn’t something we’ve thought of before. We fixed the way we hook into deprecations in #845, but since we are now never bubbling deprecations up (e.g. we don’t call At the very least we should properly document this issue (and maybe detect it for you) over in ember-cli-deprecation-workflow... |
@rwjblue should we just add the |
sure, we could do that.. |
@rwjblue which of those things do you think is best to do? |
@rwjblue let me know which you think is better. We could also do a hybrid where we call |
I'll give this one a shot |
When trying to use ember-cli-deprecation-workflow with current version of ember-inspector in Chrome 69 beta: (3.3.1), I'm trying to run:
deprecationWorkflow.flushDeprecations()
but I always get an empty list of deprecations:
If I disable ember-inspector, I get correct list of deprecations (in this case):
I would also assume that using deprecation-workflow, would prevent ember-inspector from showing
Deprecations were detected, see the Ember Inspector deprecations tab for more details.
and notifying me about silenced deprecations.All versions from Info:
Ember Inspector | 3.3.1
Ember | 3.2.2
Ember Data | 3.3.1
jQuery | 3.3.1
Ember Django Adapter | 2.0.0
Ember Simple Auth | 1.7.0
Frontend | 1.0.0+a1f1bb93
The text was updated successfully, but these errors were encountered: