-
Notifications
You must be signed in to change notification settings - Fork 79
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
Name feedback and a few suggestions #3
Comments
I think this is a great idea and i'll try to contribute. |
Another suggestion: Be able to specify starting point and some logic to handle monorepos. For example, a lot of projects using yarn workspaces will have structures like |
Would be nice to have some logic on how |
I can also imagine certain frameworks have some idiosyncrasies that won't follow the structure, so ability to ignore those. And, if running in the root, being able to ignore certain |
how about "Filer"? Has a similar ring to it as "Prettier" |
@capaj I like this name. But unfortunately it's already taken from another package :( |
@AnatoleLucet we could create a scope on npm BTW that scope is still free: https://www.npmjs.com/~filer |
Why not. With a bin named |
We've now changed name to I'm closing this issue. |
I don't think the name is that bad, but I would recommend dropping the
-cli
suffix.I've had something like this in mind ever since I ran across arkit
I think this is a great idea and could greatly simplify things for teams in the same ways prettier has.
I'm imagining adding this into my workflow as a pre-commit stage using husky + lint-staged.
Would be nice to have a flag that causes a failure on unused files, so cruft doesn't accumulate.
I think people will have strong preferences which could be solved with a couple config options, but I imagine having a consistent and enforced structure is almost universally preferable.
👍
The text was updated successfully, but these errors were encountered: