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

Adding ls-lint on an existing project ("warn" option) #63

Closed
AmirTugi opened this issue Sep 19, 2021 · 3 comments · Fixed by #66
Closed

Adding ls-lint on an existing project ("warn" option) #63

AmirTugi opened this issue Sep 19, 2021 · 3 comments · Fixed by #66
Assignees

Comments

@AmirTugi
Copy link

Hey, I would like to add this package to my project.
However, it's a big project and I want to make the migration slow-but-steady.
Is there any way to add "warn" rule like eslint just until we migrate all the badly named files/folders?

@loeffel-io
Copy link
Owner

This is a great idea - added to #36

@wburningham
Copy link
Contributor

wburningham commented Nov 8, 2021

@loeffel-io I would love to submit a PR to add this functionality. I think this can be added in a backward-compatible way that does not require a major version bump. By adding it to your v2 list are you expecting it to be non-backwards-compatible or is the v2 list just a place to add features you want to do?

@loeffel-io
Copy link
Owner

loeffel-io commented Nov 9, 2021

I would love to see a PR from you @wburningham; don't need to be in v2

wburningham added a commit to wburningham/ls-lint that referenced this issue Dec 17, 2021
loeffel-io added a commit that referenced this issue Jan 30, 2022
Initial commit to add 'warn' option for issue #63.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants