-
Notifications
You must be signed in to change notification settings - Fork 135
Document file exclusion #647
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
Conversation
a07b121 to
832029a
Compare
sharkdp
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
docs/README.md
Outdated
|
|
||
| Both `include` and `exclude` support gitignore like glob patterns: | ||
|
|
||
| - `src/` matches only a directory |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this maybe describe whether or not the directory contents would be affected?
docs/README.md
Outdated
| - `src` matches files or directories named `src` | ||
| - `*` matches any (possibly empty) sequence of characters (except `/`). | ||
| - `**` matches zero or more path components. | ||
| This sequence **must** form a single path component, so both `**a` and `b**` are invalid and will result in an error. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm very confused by this examples (**a, b**), is there some kind of context that's required here? Would it be useful to include a directory tree as an example where this example is relevant?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think a directory tree would help here. These patterns are not valid syntax. ** can only be used like /**/a but not inside a path component
2fe1c05 to
a500a6f
Compare
Summary
Document the new
src.includeandsrc.excludefields (not yet released)Note: The
includefield is currently missing in the generated docs. It will exist once my overrides PR is merged (it's when I noticed that it's missing). This is hopefully before the next release.