Add support for nullable embedded subobjects
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Scala
- Stars
- 189
- Forks
- 32
- Avg merge
- 18h 31m
- Merged PRs (30d)
- 37
Description
Currently embedded subobjects are assumed to be non-null. There are workarounds for situations which require nullability, but these aren't ideal and it would be better to provide first-class support.
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 embedded subobject handling and the existing workarounds described in the issue; no files or tests are identified in the report. Read the related implementation and tests to determine the intended nullability model, then define completion as first-class nullable embedded subobjects covered by regression tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100