Option name parsing needs to handle multiple nesting levels.
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 4.4k
- Forks
- 627
- Avg merge
- 3d 15m
- Merged PRs (30d)
- 20
Description
option (.protobuf_unittest.complex_opt1).(protobuf_unittest.corge).qux = 876;
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 option-name parsing entry point in the Wire source and compare its behavior with the nested syntax shown in the issue. Use the referenced unittest_custom_options.proto declaration as the input case; done means multiple nested option components parse successfully without breaking existing option handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100