[Bug]: Clarify how HTTP+JSON/REST returns google.protobuf.Empty
- Lingua principale
- Shell
- Stelle
- 25.7k
- Fork
- 2.6k
- Merge medio
- 3g 6h
- PR unite (30g)
- 16
Descrizione
### What happened?
Currently, the A2A specification for the HTTP+JSON/REST binding does not explicitly specify how to return successful empty responses (for operations that return google.protobuf.Empty in spec proto).
Binding requirement states that `Content-Type: application/json` is used for both requests and responses, does this mean with we should return an empty object {}? Or should it maybe be 204 No Content result.
### Relevant log output
```shell
```
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Look at the A2A specification for the HTTP+JSON/REST binding, likely in a spec or documentation directory. Find where google.protobuf.Empty return types are handled. Examine existing implementations or tests for similar operations to see current behavior. Determine whether an empty JSON object {} or a 204 No Content status is appropriate, and propose a clarification in the spec.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Ambito
- api, documentation
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 45/100