Add support for generator / processor configuration #1211
Merged
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.
Allows to configure processors (and the
Generator
itself).To kick things of the only option is to toggle the
OperationId
processorhash
flag.Default config:
Top level key must match the processor class name (with a lower case'd first char).
Settings are applied via
setXXX()
methods, so unless there is a matching method for the config option nothing will happen.A minor BC break is that the config is applied each time
Generator::getProcessors()
is called. This allows to also configure custom processors the same way.For obvious reasons,
callable
processors are skipped :)The actual BC break is that swappng the
OperationId
processor for an instance with different configuration wil no longer have any effect.On the plus side it is a lot simpler to just call
setConfig()
than swapping a processor.