Utility methods to map `ComponentSerializer` instances to new types
Open
Nobody has claimed this yet.
area: api
good first issue
type: enhancement
- Dominant language
- Java
- Stars
- 887
- Forks
- 160
- PR merge metrics
- No merged PRs in 30d
Description
Some method (or methods?) that can "wrap" a component serializer, changing the input/output/serialized types as needed.
Perhaps something like:
<I extends Component, O extends Component, R, J extends Component> ComponentSerializer<J, O, R> ComponentSerializer<I, O, R>#mapInput(Function<I, J> mapper)
Contributor guide
No contributing guide indexed for this repository
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
Start by reading the ComponentSerializer API and the proposed mapInput signature in the issue. Determine which input, output, and serialized-type mappings should be supported and whether the methods belong on ComponentSerializer. Done means the mapping API and its type parameters are clearly specified and agreed upon.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100