Refactor serialization adapter retrieval by version #1066
Merged
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 PR prepares for #1063 by moving the
initializeAdapter
declaration fromFixSerializationConfig
toSerializationVersionAdapter
. This change ensures that version-specific serializations are handled directly bySerializationVersionAdapter
, which will simplify test modifications in #1063.This transition also aligns with a clearer design, as
SerializationVersionAdapter
should be responsible for computing the appropriate adapter for each new version. This approach will help us maintain version updates withinSerializationVersionAdapter
while keepingFixSerializationConfig
unchanged.I'm uncertain if maintaining backward compatibility is necessary in the long term. If it's not needed, we can consider removing it in the future. For now, however, this PR is required to keep #1063 concise.