Remove duplicate of POJOs
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing commit 1cca9a330b08eb061d6c5e1f0bf4ed1b1622ee4f and the generated catalog POJOs from killbill/api-pojos. Trace the cyclic dependencies and identify which POJOs are duplicated as non-generated code. Done means the generated code no longer has those cyclic dependencies and the additional POJOs are removed.
Written by the indexing model from the issue text.
Description
In 1cca9a330b08eb061d6c5e1f0bf4ed1b1622ee4f, we leveraged the generated POJOs introduced from https://github.com/killbill/api-pojos, but unfortunately there are cyclic dependency with the generated catalog POJOs and this resulted in duplicating a lot of the POJOs.
The goal is to modify the generated code to prevent such cyclic dependencies and remove the additional (non generated) POJOs.
- Dominant language
- Java
- Stars
- 3
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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-catalog-plugin-test
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in killbill/killbill-catalog-plugin-test
Similar issues
-
component/data-layer
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
RegistryExceptionHandler uses self-referencing basePackageClasses instead of a controller classOpenbug finsim-registry good-first-issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
? - Needs Triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
NVIDIA/cudf-spark#17063 ·
Maintainers usually reply within 2 days
-
status:pending type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100