Consider adding @Nullable / @Nonnull annotations to generated services
- Lingua principale
- Java
- Stelle
- 12.1k
- Fork
- 4k
- Merge medio
- 2g 17h
- PR unite (30g)
- 37
Descrizione
Please answer these questions before submitting your issue.
### What version of gRPC are you using?
1.13.2
### What did you expect to see?
It would be very helpful for those of us implementing *ImplBase classes in Kotlin if the parameters of generated `rpc` methods were annotated with `@javax.annotation.Nonnull` as it gives tooling a hint that the signature of an `override` should use the non-nullable form of the parameter types.
Minor, but would make implementing services in Kotlin that bit more seamless.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start by locating the code-generation entry point for generated rpc methods and the ImplBase service classes; the issue does not name specific files or tests. Review the existing 1.13.2 generation and the discussion before deciding how @javax.annotation.Nonnull or @Nullable should be applied, then verify that generated Kotlin overrides receive the intended nullability information.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java, kotlin
- Ambito
- api
- Tipo di issue
- Funzionalità
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Attiva
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 48/100