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

reserved paths #82

Closed
jesperordrup opened this issue Feb 27, 2020 · 9 comments
Closed

reserved paths #82

jesperordrup opened this issue Feb 27, 2020 · 9 comments

Comments

@jesperordrup
Copy link

So I tried destiny on a next.js project and realized that we need to have some way to exclude folders/files.

Example, in next.js we need to keep code for pages and api in

pages
pages/api

@benawad
Copy link
Owner

benawad commented Feb 27, 2020

For now, you can accomplish that with your glob ./!(pages|server)*, but I could see adding a more friendly api to destiny for excluding files

@sQVe
Copy link
Collaborator

sQVe commented Feb 27, 2020

Duplicate of #17. Closing.

@sQVe sQVe closed this as completed Feb 27, 2020
@danielpza
Copy link
Contributor

danielpza commented Feb 27, 2020

I think it would we should have that big issue separated in small ones like this, it allows to discuss different issues without spamming or polluting the others. If we want to track them all in a single place it would be better to use github projects.

@sQVe
Copy link
Collaborator

sQVe commented Feb 27, 2020

@danielpza I agree, I had the exact same though. We should close #17 and split the relevant points in it into separate issues.

@jesperordrup
Copy link
Author

For now, you can accomplish that with your glob ./!(pages|server)*, but I could see adding a more friendly api to destiny for excluding files

I feel a need for a .destiny file

@sQVe
Copy link
Collaborator

sQVe commented Feb 27, 2020

I feel a need for a .destiny file

@jesperordrup destiny already supports a config file via https://github.com/davidtheclark/cosmiconfig but it does not currently support specifying paths in it.

@AnatoleLucet
Copy link
Collaborator

I feel a need for a Documentation 😄


Going to work on it...

@jesperordrup
Copy link
Author

For now, you can accomplish that with your glob ./!(pages|server)*, but I could see adding a more friendly api to destiny for excluding files

This will exclude the files. Which leads to a new problem. You only want to exclude them from being relocated. You still want them to be updated with new paths to all the referenced files that are moved around.

@AnatoleLucet
Copy link
Collaborator

@jesperordrup #70 ?

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

5 participants