new builder options: tagNameProcessors and attrNameProcessors #462
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
processItem
was always used in the same way, removed some copied codepackage-lock.json
to.gitignore
to make git handling simpler. (If you want, we can revert this.)for key, entry of child
inbuilder.coffee
- should it befor own key...
?README.md
.Potential issues:
tagNameProcessors
andattrNameProcessors
. After this pull request, such users may run into problems because their builder modifies the names in unexpected ways.Possible remedies:
builderTagNameProcessors
andbuilderAttrNameProcessors
.tagNameProcessors
andattrNameProcessors
in the builder, e.g.builderProcessors: true
orversion: "0.4.20"
. Old code doesn't contain this option and thus works as usual.README.md