`generateKotlinNullableClasses` should still generate nice `toString` for objects
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 217
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
When using generateKotlinNullableClasses, it becomes impossible to use toString in the debugger to view the full scope of all the fields that were actually accessed.
It would be nice if the generated functions held information whether or not the field were present or not, that way, a sane toString could be generated that checks if each field were present before adding it to the printed string.
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 locating the implementation of generateKotlinNullableClasses and the generated model toString logic. Inspect how field presence is represented, then verify that generated toString output includes only fields that were accessed and handles absent fields sensibly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100