-
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
spago build
appears to include the test directory of (local) dependencies
#102
Comments
Sorry, ignore this - I'm being an idiot. |
No problem! 🙂 |
I had some existing local dependencies that I was converting to try out spago. |
I have done this a few times too. It's no biggy, but maybe init with files shouldn't create a main.purs?. |
Or, perhaps it should by default but there should be a flag to prevent
that.
|
How about detecting if |
Let's step back and consider the different reasons why this would be useful and annoying. If one is migrating from psc-package to spago, then it's probable that the user already has their project structure set up correctly. They simply want to migrate to spago. Thus, adding a Main.purs file would be annoying to them. If one is starting a new project via spago, then it would be nice if spago created all the necessary project structure: Others might want to use spago to write a library (as that can be done now via So, there are a few options here:
|
@JordanMartinez good points 👍 A small note first: the detection "can we migrate a psc-package file" doesn't happen specifically in the Also I would like to keep the CLI-surface as small as possible, and I wouldn't like to add another command that does almost the same thing as So there's a "fix" up in #105, I went with checking if |
Thanks for the clarification! |
I'm getting a compilation error saying that
Main
has been defined multiple times and it's pointing at the test directory of my local dependencies.The text was updated successfully, but these errors were encountered: