Fix UseSystemTextJsonForSerialization customization #720
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
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.
UseSystemTextJsonForSerializationconfiguration isn't respecting any configuration passed in for Azure Service Bus (and possibly other messaging options). This is because the initialWolverineOptionscalls over toUseSystemTextJsonForSerializationwithout any parameters, so_defaultSerializergets set. Then the??=means it never takes the right side.This should resolve this issue.
(I briefly looked at creating a test for this, but I wasn't sure if it might belong under configuration or serialization tests... categorization is hard)
Closes #717