Skip to content
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

Closed
jurecuhalev opened this issue Aug 6, 2018 · 6 comments
Closed

Problems with ember-cli-deprecation-workflow #857

jurecuhalev opened this issue Aug 6, 2018 · 6 comments

Comments

@jurecuhalev
Copy link

jurecuhalev commented Aug 6, 2018

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:

"window.deprecationWorkflow = window.deprecationWorkflow || {};
window.deprecationWorkflow.config = {
  workflow: [

  ]
};"

If I disable ember-inspector, I get correct list of deprecations (in this case):

window.deprecationWorkflow = window.deprecationWorkflow || {};
window.deprecationWorkflow.config = {
  workflow: [
    { handler: "silence", matchId: "ember-routing.route-router" }
  ]
};

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

@rwjblue
Copy link
Member

rwjblue commented Aug 6, 2018

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 next‘) things like ember-cli-deprecation-workflow’s flushDeprecations` does not work (since it just never saw any deprecations).

At the very least we should properly document this issue (and maybe detect it for you) over in ember-cli-deprecation-workflow...

@RobbieTheWagner
Copy link
Member

@rwjblue should we just add the next() call perhaps or add in a way to let them come through for this use case? Maybe even just add a button to call flushDeprecations from the deprecations tab of inspector?

@rwjblue
Copy link
Member

rwjblue commented Aug 30, 2018

sure, we could do that..

@RobbieTheWagner
Copy link
Member

@rwjblue which of those things do you think is best to do?

@RobbieTheWagner
Copy link
Member

@rwjblue let me know which you think is better. We could also do a hybrid where we call next to allow them through, but then have a setting to either show them in the console or not.

@robustdj
Copy link
Contributor

I'll give this one a shot

robustdj added a commit to robustdj/ember-inspector that referenced this issue Mar 18, 2019
robustdj added a commit to robustdj/ember-inspector that referenced this issue Mar 18, 2019
RobbieTheWagner pushed a commit that referenced this issue Mar 19, 2019
* Bubble up deprecations for ember-deprecation-workflow (#857)

* Add a checkbox to toggle ember deprecation workflow (#857)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants