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
Instead of running the ember-cli-eslint blueprint on ember new we should instead just duplicate the empty ESLint config files so that e.g. they show up at https://github.com/ember-cli/ember-new-output and also work with the --skip-npm flag.
The text was updated successfully, but these errors were encountered:
We discussed this before, but remind me. Why can't we just run the generator as part of the release process? It would show up in the npm dist, and we don't have to commit to master and maintain duplicates.
tl;dr is that I think KISS might make sense here instead of making it infinitely complex just to save us from duplicating two files with 18 lines in total...
Instead of running the
ember-cli-eslint
blueprint onember new
we should instead just duplicate the empty ESLint config files so that e.g. they show up at https://github.com/ember-cli/ember-new-output and also work with the--skip-npm
flag.The text was updated successfully, but these errors were encountered: