-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Idea: Separate purs compile
flags somehow
#353
Comments
purs compile
flags somehow
Yeah this sounds like not the ideal behaviour. I'd say we'd want to keep the This is the code for the passthrough stuff: |
According to
To me it seems like we can't (and possibly shouldn't) force these arguments to be passed after the It would be possible to use |
@googleson78 great points. We already have the behaviour you suggest in your first post for the node arguments, so introducing it for |
What do you think about separating flags passed to
purs compile
explicitly in some way, for example with--purs-compile-flags=
?Right now
--help
says you should use--
if you want to specify that something should go topurs compile
, but what really confused me is that it is not mandatory to separate them with--
.Running
spago build src/X.purs src/Y.purs
works fine - which is not immediately obvious when looking atspago build --help
(it has no mentions of files as arguments).This was especially problematic when I tried
spago build --watch --path src/**/*.purs
, only to see how not all of my files were "being watched". In reality only the first file from the expanded glob is being watched, because--path
accepts only one file - the rest are passed ontopurs compile
, allowing compilation to proceed without errors (or at least that's what I think is going on here).The text was updated successfully, but these errors were encountered: