Create POJOs for (some) interfaces
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java
- Domain
- backend-api-design
Research direction
Start by reviewing the interfaces in the catalog module, beginning with Plan.java and its linked API definition. Identify which interfaces are in scope and confirm the proposed POJO naming and constructor requirements before implementing. Done means each agreed POJO has a default constructor, an all-fields constructor, private final fields, toString, equals, and hashCode.
Written by the indexing model from the issue text.
Description
We would like to start by creating POJOs matching the interfaces we have defined in our catalog module. For instance, given the interface Plan, we would like to create a class ApiPlan (this is a suggestion for the naming, perhaps there is something better) that implements the interface.
The goal is to make it easier for folks writing plugin and avoid having them to write all kinds of POJOs themselves.
Each of these POJO would need to have:
- Default CTOR
- CTOR with all fields
- All fields
private final toStringmethodequalsandhashCodemethod
- Dominant language
- Java
- Stars
- 20
- Forks
- 39
- Avg merge
- 18h 56m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from killbill/killbill-api
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
killbill/killbill-api#120 ·
All issues in killbill/killbill-api
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
liquid-java/liquidjava#321 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OpenConext/OpenConext-access#1015 ·
Maintainers usually reply within 1 day
-
68000: FDBcc branch target is 2 bytes too low (uses inst_start+2 instead of the displacement word)Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NationalSecurityAgency/ghidra#9702 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
apache/rocketmq-dashboard#5358 ·
Maintainers usually reply within 3 days