Serialization should be done the same way for all types
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
Originally by @Artur-
Currently serialization/deserialization code is generated on the client side for SharedState types and types they refer to. Some types like Map, List, arrays are handled in other parts of the framework. It would be much clearer if all types were handled in the same way i.e. one serializer class per type. There is no need to generate the serializers for standard types but they should implement the same interface as the generated serializers.
Imported from https://dev.vaadin.com/ issue #8449
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files or tests. Start by locating client-side serialization for SharedState types and the separate handling for Map, List, and arrays, then compare their interfaces; done means standard and generated types follow the same serializer interface without generating serializers for standard types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100