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
Improving ignore pattern documentation and UX for Windows users #8139
Comments
No need to convert the slashes as most windows users(who are using git) are already used to it. But I believe that the documentation should state clearly that |
Thanks @borela for your feedback. I think we can turn this into a documentation-only issue, and we can discuss any core code changes elsewhere. So I've marked the issue "accepted" and added "help wanted" label as well. Thanks! |
Hi! @platinumazure what are the changes you are suggesting exactly? Is this still relevant? |
Hi @santanaG, thanks for commenting. The general idea is this: In our .eslintignore documentation, we want to make it clear that the syntax is the same as .gitignore (and, in particular, that all paths should use forward slash as the path separator). As far as I know, this is still relevant. Hope this helps! |
# Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # # On branch gitignore-syntax-updates # Changes to be committed: #modified: docs/user-guide/command-line-interface.md #modified: docs/user-guide/configuring.md # Adds cross links between .eslintignore and --ignore-pattern sections. Adds link to --ignore-pattern section directing to .gitignore specs. Adds description to .eslintignore section that emphasizes forward slashes being necessary with examples of valid and invalid syntax. Adds explicit statements to both sections that support this example.
Inspired by #8135. Root cause of that issue was that the user was using a Windows path (with backslash delimiters) as an ignore pattern (which require forward slash delimiters).
Currently we use node-ignore to provide support for gitignore style patterns. Should we consider expanding that to support Windows paths (basically replacing \ with / before feeding the patterns to node-ignore)? Or would that add too much confusion?
Observations about current documentation (as of 2/23/2017):
--ignore-pattern
do use the term "patterns" rather than "paths", but no direct mention of gitignore syntax. It does mention that it's the same format as .eslintignore, but no cross-linking. I think that would be an easy fix.Any other documentation we should update?
The text was updated successfully, but these errors were encountered: