a2aproject / a2aproject/A2A

[Bug]: Clarify how HTTP+JSON/REST returns google.protobuf.Empty

Offen
#1,674 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Shell
Sterne
25.7k
Forks
2.6k
Ø Merge
3 T. 6 Std.
Gemergte PRs (30 T.)
16

Beschreibung

### 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

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Bereich
api, documentation
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
45/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.