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

added config.ignorePatterns option #326

Merged
merged 1 commit into from
Oct 22, 2012
Merged

added config.ignorePatterns option #326

merged 1 commit into from
Oct 22, 2012

Conversation

Delapouite
Copy link
Contributor

ignorePatterns argument for balUtil.scandir is not hardcoded to true anymore and can be tweak to a custom regex
It defaults to true in the initial config to preserve the previous behavior.

Improve the situation described in issue #193
The commonPatterns regex reference was added to the balUtil wiki : https://github.com/balupton/bal-util/wiki

balupton added a commit that referenced this pull request Oct 22, 2012
added config.ignorePatterns option
@balupton balupton merged commit 8d8118c into docpad:dev Oct 22, 2012
@balupton
Copy link
Member

Published to v6.8.3

balupton added a commit that referenced this pull request Oct 22, 2012
- v6.8.3 October 22, 2012
	- Fixed growl generating notification from saying `generated` instead
of `generating`
	- Added `ignorePatterns` option
		- Closes [#193](#193) thanks to
[Bruno Héridet](https://github.com/Delapouite) for [pull request
#326](#326)
@balupton
Copy link
Member

As of v6.19 we now have the configuration options ignoreCommonPatterns and ignoreCustomPatterns

balupton added a commit that referenced this pull request Oct 23, 2013
added config.ignorePatterns option
balupton added a commit that referenced this pull request Oct 23, 2013
- v6.8.3 October 22, 2012
	- Fixed growl generating notification from saying `generated` instead
of `generating`
	- Added `ignorePatterns` option
		- Closes [#193](#193) thanks to
[Bruno Héridet](https://github.com/Delapouite) for [pull request
#326](#326)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants