Add config to specify user defined mapping of field names to generated field names.
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 217
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
This is to avoid keyword clashes for fields that have the same name as kotlin/java keyworkds, e.g void, default etc.
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
The issue names no files, tests, or configuration entry points. Start by locating how configuration is defined and how field names are generated, then determine how a user-supplied mapping should be represented and verified for Kotlin and Java keyword clashes; done means configured mappings produce the requested generated names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kotlin
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100