EsotericSoftware/kryo

VersionedRecordSerializer?

Open

#884 opened on Feb 14, 2022

View on GitHub
 (11 comments) (0 reactions) (0 assignees)HTML (816 forks)batch import
feature requesthelp wanted

Repository metrics

Stars
 (6,052 stars)
PR merge metrics
 (Avg merge 107d 5h) (9 merged PRs in 30d)

Description

Is your feature request related to a problem? Please describe. I'm trying to serialize a Record that evolves - new components are being added to it.

Describe the solution you'd like Would it make sense to create a VersionedRecordSerializer akin to VersionedFieldSerializer with the same functionality, the @Since annotation?

Describe alternatives you've considered An obvious workaround is to use a traditional class instead of a record.

Contributor guide

Research direction
Study the implementation of VersionedFieldSerializer and the @Since annotation, then design a similar serializer for Java records that supports versioning.
Tech stack
java
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaKryo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60