networknt / networknt/light-codegen
Unclear distinction between generator modules and codegen application.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 49
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
From the readme (in progress of reviewing), i'm learning that a few of the folders in this projects more closely resemble sample/example code (for example light-rest-4j), and doesn't necessarily apply to the codegen functionality.
It was also a surprise to see light-hybrid-4j, a project which is functionally an api container, to be included in this repo.
Maybe it could be a consideration to split this up into light-codegen-demo, light-codegen, and you already have a light-hybrid-4j, so ... not sure.
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
Review the README and compare the light-rest-4j and light-hybrid-4j folders with the codegen functionality they contain. Define clear boundaries for light-codegen-demo, light-codegen, and light-hybrid-4j, then document the agreed repository structure and migration implications. Done means the project organization and purpose of each module are unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100