Make initial config file generation easier.

[rwjblue]

Copy and paste from the console kinda sucks. We can do better.

How?

[raytiley]

can plugins interact w/ the file system? Would be cool if there was a tab in ember inspector that allowed you to diff your current deprication-workflow.js and add / remove / generate the file from there.

[rwjblue]

Definitely agree. We could add to https://github.com/emberjs/ember-inspector/issues/430.

[jakehow]

@rwjblue simple way to make this better on one dimension easily, is print out instructions in the console post test run for deprecationWorkflow.flushDeprecations(), I keep having to come back to the github repo to lookup the method name and copy and paste it.

[rwjblue]

@jakehow - I'm game.

[ssendev]

another thing to make it easier would be if already registered deprecations would not be listed or get added to the list. use case beeing not having a test suite which collects all deprecations at once and instead scraping them from several pages.

it would help when regexps were added manually which catch several deprecations e.g. /You attempted to set '.*\' from '.*', but object proxying is deprecated. Please use 'model\..*' instead./. another helpful thing would be if messages that contain ember objects with id would be a regexp by default. <my-app@controller:application::ember\d+>