Field interface
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
When I manipulate list of fields I often need to cast fields because all fields have not common interface/class except HasValue but HasValue is not a component.
The idea is to have Field that inherit HasValue + Component
A lot of fields inherit of AbstractField but not all...
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
Start by reviewing HasValue, Component, AbstractField, and the field implementations; the issue names no specific files or tests. Determine the scope of a common Field interface and how fields that do not inherit AbstractField would adopt it. Done should be defined by agreement on the interface and consistent support across the relevant field types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100