Default glob pattern like standard
See original GitHub issueWould love to have prettier-standard use the same default glob pattern as standard itself:
by default standard will look for all files matching the patterns: **/.js, **/.jsx.
Certain paths (node_modules/, coverage/, vendor/, *.min.js, bundle.js, and files/folders that begin with . like .git/) are automatically ignored. Paths in a project’s root .gitignore file are also automatically ignored.
This would make running prettier-standard
operate similar to standard
(no options necessary, just normal conventional configuration by default)
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
glob — Unix style pathname pattern expansion
The glob module finds all the pathnames matching a specified pattern according to the rules used by the Unix shell, although results are...
Read more >glob - Greg's Wiki
"Glob" is the common name for a set of Bash features that match or expand specific types of patterns. Some synonyms for globbing...
Read more >Shell GLOB patterns (wildcard pathname matching) - Teaching
GLOB patterns do not only match file names. The names being matched by a GLOB pattern can be anything: files, directories, symbolic links,...
Read more >A Beginner's Guide: Glob Patterns
Globs, also known as glob patterns are patterns that can expand a wildcard pattern into a list of pathnames that match the given...
Read more >Using glob pattern matching - Centrify Product Documentation
The default glob pattern matching enables you to specify a string using wild card characters. For example, with glob pattern matching, the command...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Isn’t that pretty common across most unix tools? (that usage info is only printed when
--help
is passed?)Without dismissing the value of discoverability, the help output is only useful for people on their first-ever run; likely just poking around. Every invocation after that, they’re intending to actually run the formatter. This should be optimized for the 90% use case (which is actually running the formatter), not the .1% use case of getting help. (Which is already conventionally available via
--help
like every other *nix CLI)standard
itself does this, and isn’t this tool supposed to be part and parcel with standard? (not to mention, *nix convention)Yes, I’ll close this issue. The problem is Unix tools don’t change anything by default and prettier-standard would automatically format all .js files if I made this a default, which can be annoying.
The
--lint
issue is already there: https://github.com/sheerun/prettier-standard/issues/17