Skip to content
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

How does your develop-test cycle work? #36

Open
JeffreyBenjaminBrown opened this issue Oct 29, 2018 · 2 comments
Open

How does your develop-test cycle work? #36

JeffreyBenjaminBrown opened this issue Oct 29, 2018 · 2 comments

Comments

@JeffreyBenjaminBrown
Copy link

I installed toodles globally, via cabal. Then I filed a bunch of issues, and felt like I ought to try contributing, so I cloned the source and made a tiny change (started to subdivide the code into modules, beginning by moving the types and instances to a separate file), and realized I don't know how to try out my changes.

I tried using "stack run toodles", and it works, but it scans the toodles folder. I'd like it to scan a different folder, but I can't figure out how to pass in the --directory= argument.

Should I remove that global installation, and run "stack install toodles" every time I want to try a changed version?

@aviaviavi
Copy link
Owner

Awesome that you'd like to contribute 😀. My workflow doesn't interfere with any global toodles installation, so you can leave that as is.

My workflow:

  1. Make some changes
  2. stack build --fast && stack exec toodles -- -d <directory> Any args you want to pass to the end binary with stack goes after the --, which seems like the key piece of info you needed
  3. repeat

@JeffreyBenjaminBrown
Copy link
Author

JeffreyBenjaminBrown commented Oct 30, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants