#483 Support DoNoSerialize by pattern #496
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…duced a new settings key DoNoSerializePatterns to avoid messing with the exsting one.
…hin the expression.
|
@KevinJump |
|
This looks good, I will run some tests and we will fold it into the next release. |
|
Good to hear. I believe you'll cherrypick it into v10 as well? 😊 |
|
Yeah we will get this into the v10 release too. |
KevinJump
pushed a commit
that referenced
this pull request
May 11, 2023
* #483 added regex support to the DoNoSerialize settings.Introduced a new settings key DoNoSerializePatterns to avoid messing with the exsting one. * Simplify by allowing a single pattern instead as that can be done within the expression. * Correct key name; now it's a singular. * cleanup method name --------- Co-authored-by: Ayham Fakihani <af@frankly.dk>
|
in v10.6 and v11.2 (both released now) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Introduced a new settings key "DoNotSerializePattern" which can be used to exclude properties based on a regex expression.
Reason for not using the existing settings entry is not to mess with the performance of the serialization in any way (unless consumer opts in for use the pattern exclusion).
Example value:
{ "Settings": { "DoNotSerialize": "serverName,supportEmail", "DoNotSerializePattern": "(?i)[a-z]+_(localProp|envProp)" } }