You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after digging in it seems the issue with not being able to register a handler was that ember-cli-deprecation-workflow was (IS still until https://github.com/mixonic/ember-cli-deprecation-workflow/pull/107/files lands) using ember-debug-handlers-polyfill which appears to clobber the deprecation handler in newer versions of ember (at least as of a year ago), potentially due to issues around ember global vs ember modules.
Filing for @runspired
At https://github.com/ember-polyfills/ember-debug-handlers-polyfill/blob/master/vendor/ember-debug-handlers-polyfill/debug.js the implementation of the registerDeprecationHandler system is indeed squashed on the
Ember
global, but should only squashed if a prior implementation is not found https://github.com/ember-polyfills/ember-debug-handlers-polyfill/blob/master/vendor/ember-debug-handlers-polyfill/debug.js#L135I haven't confirmed this, or what versions of Ember it impacts. Maybe @runspired has more.
The text was updated successfully, but these errors were encountered: