lucky icon indicating copy to clipboard operation
lucky copied to clipboard

If using `lucky watch` directly, tell users to use `lucky dev`

Open paulcsmith opened this issue 6 years ago • 2 comments

https://gitter.im/luckyframework/Lobby?at=5d408aa5c356af25e0580790

It is unclear what the best option is here. Maybe we print a warning if using lucky watch without a specific flag? Maybe an ENV var is set?

The ENV var might be nice because if you prefer to use lucky watch in all your projects you can export it in your shell. SILENCE_LUCKY_WATCH_WARNING=true or something likethat

paulcsmith avatar Jul 30 '19 19:07 paulcsmith

@jwoertink

paulcsmith avatar Jul 30 '19 19:07 paulcsmith

TL;DR: Someone generated a lucky project and ran lucky watch. The assets never built, and caused issues.

Now, funny thing, I have to run lucky watch directly because my assets take so long to build that running lucky dev can cause issues. That's related to this issue.

I think outputting a warning that says "running lucky watch directly does not compile assets. .... " (but actually well written), then we can look for that env var to ignore that warning. That should be fine enough in this case.

jwoertink avatar Oct 24 '19 17:10 jwoertink