How appropriate would it be to allow a new argument which prevents stack from triggering a rebuild when a test suite changes?
During development of a web app using yesod, we're in the situation where I'm running the server with yesod devel (which uses stack ... --file-watch underneath).
Our selenium test suite is attached to the server devel is running. I'm altering some selenium tests which I have loaded with GHCi. When I change the selenium tests, stack notices, which signals to devel that a rebuild is required even though it's not! This really just slows down development.
I propose something like stack build --file-watch --no-watch-tests . What do you think?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4