This repository has been archived by the owner on Jun 5, 2024. It is now read-only.
Add the current class scope to custom mutator functions #20
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.
This way you could use the default
RequestBody
class scope to e.g. useextractFirstValueMutator
in a custom-filter's value mutator without duplicating it or use other magic based on the currentRequestBody
class instance.For example: If I'd like to use the default
extractFirstValueMutator
in a custom filter I currently need to duplicate this functionality. With the scope added to the message usingcall
we can just write smth like: