Skip to content

How does your develop-test cycle work? #36

Open
@JeffreyBenjaminBrown

Description

@JeffreyBenjaminBrown

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?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions