Log SKIP_EMBER when true in Development about ember-cli-rails HOT 6 OPEN

Or, if we should just warn regardless when in development, we could add a method that does the check and warn if true, then call it in

Seems like it could still be useful to warn, even if the build is successful.

from ember-cli-rails.

If interested, I would be more than happy to work on a PR, it would be a feature that could likely save our team time in the future.

from ember-cli-rails.

@Samsinite I like this idea!

How would we structure the communication of how the application is configured?

ember-cli outputs a block of dependencies and version numbers at the start of commands like ember serve and ember test, were you thinking of something similar?

from ember-cli-rails.

Honestly, I haven't put a lot of thought into the structure of the log message. What would you prefer the log message to look like or say?

from ember-cli-rails.

Honestly, I haven't put a lot of thought into the structure of the log message. What would you prefer the log message to look like or say?

I'm less focussed on the structure of the log message, and more thinking about when and how it should be communicated.

Just ran into an issue where a co-worker accidentally had SKIP_EMBER=true in development, and it took us 20 minutes to track down.

At what point in the process would some indication that SKIP_EMBER=true be most helpful?

from ember-cli-rails.

What about adding a check for app.development? and app.skip? here:

Thoughts? Unless I am mistaken, the current gem structure should make this feature fairly straight forward.

from ember-cli-rails.