ember-cli-deprecation-workflow
ember-cli-deprecation-workflow copied to clipboard
mixonic
Configuration like so: ``` { handler: 'silence', matchId: 'template-compiler.registerPlugin' }, ``` But getting a bunch of these: ``` DEPRECATION: Using class based template compilation plugins is deprecated, please update to...
Is it possible to automate what this addon provides even further? For example, we could [write test output to a log](https://github.com/narayanpai/testem-log-reporter), run `flushDeprecations()` against that log, and then diff against...
This seems like a timing issue in tests. Have both of these in the config file. ``` { handler: 'silence', matchId: 'ember-global' }, { handler: 'silence', matchMessage: /Usage of the...
If you don't have a test suite to run its very hard to figure out what goes in that file.
By default, ember-cli adds the following to `.eslintrc.js`: ```js // node files { env: { browser: false, node: true, }, files: [ 'ember-cli-build.js', 'testem.js', 'blueprints/*/index.js', 'config/**/*.js', 'lib/*/index.js', ], parserOptions: {...
I just tried installing the 2.0.0-beta.2, and run `deprecationWorkflow.flushDeprecations()` as the readme says, but it complains that `deprecationWorkflow` is not defined for me?
The output of `flushDeprecations()` no longer formats in a way that can be copied and pasted into the config file. We now get the raw string, which indicates this is...
Howdy folks 👋 I've seen a few people suggest custom handlers in issues, and some of them are good ideas but I can understand the reluctance to add more and...
Can we include a handler called `showOnce` to log each handled deprecation at least once? This is useful for users to see the deprecations while testing or developing at least...
