Skip to content

feat(forms)!: forms answers list is a listing like every other, and columns-list gives its columns - #574

Merged
bim-ba merged 1 commit into
mainfrom
feat/forms-answers-columns
Oct 10, 2026
Merged

bim-ba merged 1 commit into
mainfrom
feat/forms-answers-columns

Conversation

@bim-ba

@bim-ba bim-ba commented Oct 10, 2026

Copy link
Copy Markdown
Owner

Decision 3-Б of #538: the last listing that could not go on from a token.

What changes

forms answers list SURVEY_ID (keeps its name) forms answers columns-list SURVEY_ID (new)
Returns the answers, with --limit, --all, --next like every listing the columns the cells of an answer stand in
-o json {items: [{id, created, uid, data}], truncated, next, total} [{id, slug, type, text, has_scores}, …]
Options as before, plus --next --questions, --use-slugs: the two that change the columns
MCP forms_answers_list forms_answers_columns_list
SDK forms.answers.list(...) → Listing[Answer] forms.answers.columns_list(...) → ItemList[Column]
-o name answer ids column ids

The name is columns-list, not columns as the example in #538 wrote it: the repository names an operation of a sub-thing this way (integrations-list beside it, fields-list, tags-list).

Breaking

  • CLI: forms answers list -o json printed {columns, answers, next}; it prints the listing object. A script reads .items[] where it read .answers[], and takes the columns from forms answers columns-list.
  • SDK: forms.answers.list() returned AnswersResponse; it returns Listing[Answer].
  • MCP: forms_answers_list returns the listing object and takes all and next.

The cells and the columns

The cells of an answer (data) are positional. After the split the answers alone do not say what a cell is, so the help of list (command, tool and method) says that the positions are those of columns-list asked with the same --questions and --use-slugs, and names --answer-format raw, which keys the data by question and needs no columns. There is no joining code. A test holds the claim: asked the same way, an answer has as many cells as columns-list gives columns.

columns-list sends the same GET /surveys/{id}/answers with page_size=1: the API has no request for the columns alone, so one answer is read to learn them and left out; its help says so. Against the mock, a form with no answers at all returns its columns all the same (a contract case). Couldn't verify live: the test organization has no form.

The listing exception is gone

forms.answers.list is removed from ARCH1_LISTINGS_WITHOUT_NEXT in tests/architecture/test_arch1.py; one entry is left there (wiki.comments.thread_list). No other file named the exception.

One published operation, two ycli operations

Measured, not only read: tests/tooling/test_api_drift.py passes with no new entry in EXPLAINED or NOT_WRAPPED, and the README numbers for Forms stay "84 of 84 published operations wrapped, 8 differ". compare() in scripts/api_drift.py collects the calls of a published operation into a list and compares their union, so two operations sending the same published GET is what it is written for.

Also here

  • Answer.id and Column.id get the Identity() mark, so both listings print names. I had told the architect Answer.id was already marked; it was not, and tests/architecture/test_names.py failed on it until it was. Column.id is taken to be the question id --questions accepts: not verified live.
  • The live scenario e2e/scenarios/forms/survey_options.yaml expects the listing object and has a step for columns-list. It collects in an environment without extras (30 scenarios); it was not run.
  • The Forms skill names the new command; generated copies, reference, examples, snapshots and the README coverage (468 operations, Forms 86) are regenerated.

Checked

  • uv run pytest: 7020 passed, 5 skipped, coverage 100% (lines and branches); lint-imports, ty, ruff clean; pre-commit hooks passed. That run was on this tree; only the squash followed it.
  • Seen failing on its defect, then restored: the listing without next (the ARCH-1 check of listings failed); columns-list not passing --questions / --use-slugs (the positions test failed).

Not run

  • No live call to Forms; the e2e scenarios.

🤖 Generated with Claude Code

… `columns-list` gives its columns

The answers of a form are listed with the three handles of every listing: `--limit`, `--all` and `--next` in the CLI, `limit` / `all` / `next` in the tool, a lazy `Listing[Answer]` in the SDK. The columns the cells of an answer stand in are read by a command of their own, `forms answers columns-list` (`forms_answers_columns_list`, `forms.answers.columns_list`): the API has no request for them alone, so it reads one answer to learn them.

BREAKING CHANGE: `forms answers list -o json` prints `{items, truncated, next, total}` instead of `{columns, answers, next}`: a script reads `.items[]` where it read `.answers[]`, and takes the columns from `forms answers columns-list`. `forms.answers.list()` returns `Listing[Answer]` instead of `AnswersResponse`, and the tool `forms_answers_list` returns the listing object.

Decision 3-Б of #538.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch was previously deployed

1 inactive deployment
yandex-e2e — 7be6a781 Deployed Oct 10, 2026 by bim-ba via live (all) #708
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant