docs(spec): use canonical TaskState enum name in Input Required prose - #2155
Open
madankumarpichamuthu wants to merge 4 commits into
Open
madankumarpichamuthu wants to merge 4 commits into
madankumarpichamuthu wants to merge 4 commits into
Conversation
The Input Required State description in section 3 referred to the state as `input-required` (the v0.3.0 kebab-case form) while the normative TaskState enum and all section 6 JSON examples use the ProtoJSON SCREAMING_SNAKE_CASE name. Align the prose with `TASK_STATE_INPUT_REQUIRED` so the specification uses one consistent form. Refs a2aproject#1408
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Follow-up to #1408. When #1408 was filed, the section 6 JSON examples used the old v0.3.0 kebab-case task states. Those examples have since been corrected to the ProtoJSON
TASK_STATE_*form, but one prose reference was missed:The normative
TaskStateenum (§4.1.3) and every JSON example in §6 useTASK_STATE_INPUT_REQUIRED. This aligns the remaining prose reference with that canonical form so the specification uses one consistent spelling.Scope kept intentionally narrow to
docs/specification.md. Conceptual topic pages (e.g. Life of a Task, Streaming) still use the shortinput-requiredphrasing as readable prose; those are left untouched to avoid a broader style change. If maintainers consider #1408 already resolved by the earlier example fixes, this PR can simply close it out.Checklist
CONTRIBUTINGGuide.docs(spec):forspecification.md).Closes #1408