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

Documentation on best/common way to integrate into a project #144

Open
andria-dev opened this issue May 24, 2020 · 1 comment
Open

Documentation on best/common way to integrate into a project #144

andria-dev opened this issue May 24, 2020 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@andria-dev
Copy link

As it currently stands, I can't seem to find a great way to integrate Destiny into a project. When should I be running Destiny? I mean, ideally, it would be whenever an import is changed or when a file is referenced/created.

The only way I've found to run it consistently is to run it on pre-commit with husky, is that the best practice currently? What do you do for this repo?

All of this information might be useful in your documentation.

@AnatoleLucet AnatoleLucet added the documentation Improvements or additions to documentation label May 25, 2020
@AnatoleLucet
Copy link
Collaborator

On this repo will still manualy run Destiny on src. But maybe a day we'll switch to a lint stage or a husky hook. I personally use it that way on another project.

A watch mode has been mentioned in #17. It could be a possible way to use it.

There's also a discussion in #112 about a "flat structure" on the remote repo.

I though about an IDE plugin, but I don't know if it would be viable.

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

No branches or pull requests

2 participants