Add field exclusion strategy for SnippetController #7287
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
mamazu
force-pushed
the
field_exclusion
branch
3 times, most recently
from
6a1578f
to
2973375
Compare
|
@alexander-schranz Do you think we can also get this shipped in 2.6 maybe? |
alexander-schranz
force-pushed
the
field_exclusion
branch
from
2573b63
to
3a15954
Compare
alexander-schranz
approved these changes
Mar 29, 2024
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.
What's in this PR?
Adding code to only serialize fields specified in the request of the snippet controller.
Why?
When using the snippet listing by default it also serializes the content which is very slow. This PR adds an exclusion strategy that will not serialize the content anymore.
To Do