fix: Default JSON serializer instance is not affected by any global settings. #2613
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
…ettings. This partially superceeds #2610 and it's a better approach overall as our serializar is not created using the global settings at all, so we don't need to override global settings. Note that JsonConvert.Deserialize uses JsonSerializer.CreateDefault that relies on global settings, and then applies any specific settings. In turn we use JsonSerializer.Create that only applies specific settings. By not using JsonConvert we have stopped being affected by global settings at all. The test from #2610 remains and proves this approach works. Possibly fixes #2611
jskeet
approved these changes
Nov 17, 2023
amanda-tarafa
added a commit
that referenced
this pull request
Jan 9, 2024
Fixes: - #2613 Default JSON serializer is not affected by gloabl JSON settings. - #2630 Tune authorization token staleness and validity windows so that it doesn't overlap with Metadata Server authorization token caching. Features: - #2616 Makes batch response handling more efficient, particularly benefiting large responses.
amanda-tarafa
added a commit
that referenced
this pull request
Jan 9, 2024
Fixes: - #2613 Default JSON serializer is not affected by gloabl JSON settings. - #2630 Tune authorization token staleness and validity windows so that it doesn't overlap with Metadata Server authorization token caching. Features: - #2616 Makes batch response handling more efficient, particularly benefiting large responses.
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.
This partially superceeds #2610 and it's a better approach overall as our serializar is not created using the global settings at all, so we don't need to override global settings. Note that JsonConvert.Deserialize uses JsonSerializer.CreateDefault that relies on global settings, and then applies any specific settings. In turn we use JsonSerializer.Create that only applies specific settings. By not using JsonConvert we have stopped being affected by global settings at all. The test from #2610 remains and proves this approach works.
Possibly fixes #2611