docs(builder-agent): document REST-bound and cascading JSON Form dropdowns#36
Closed
ZackStr wants to merge 1 commit into
Closed
docs(builder-agent): document REST-bound and cascading JSON Form dropdowns#36ZackStr wants to merge 1 commit into
ZackStr wants to merge 1 commit into
Conversation
…downs
Adds a new helper template (create-json-form-rest-bound.json) for forms
whose dropdowns are populated from live IAP endpoints, including the
cascading pattern where one dropdown's URL path parameter is fed by
another field's selection.
Builder-agent SKILL.md updates:
- Endpoint table gains GET /forms/{id} and bulk DELETE /json-forms/forms
(body {"ids":[...]} — there is no per-id DELETE)
- New "REST-bound dropdowns" subsection covering struct/bindingSchema
mirroring, the :name path-param syntax (not {name}), the variables[]
cascade mechanism with reference JSON pointers, the DependencyWidget
ui:widget requirement on both source and dependent fields, and
/automation-studio/json-forms/method-options for endpoint discovery
- Templates table now lists both create-json-form.json (static) and
create-json-form-rest-bound.json (REST-bound/cascading)
- One-line comment in the static helper redirecting readers to the new
helper when bindingSchema must not be empty
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 6, 2026
Contributor
|
Closing in favor of creating an independent skills for JSON Forms. |
5 tasks
ZackStr
added a commit
to ZackStr/builder-skills
that referenced
this pull request
May 11, 2026
Re-opens itential#36 per @keepithuman's review: instead of expanding builder-agent with REST-bound and cascading dropdown details, the JSON Forms application gets its own skill. The new skill (.claude/skills/app-json_forms/SKILL.md) covers the full form structure (struct / schema / uiSchema / bindingSchema), the three dropdown patterns (static-enum, REST-bound, cascading), the API reference (including the bulk-only DELETE that returns 404 on per-id calls), update semantics (`{"options": ...}` wrapper with full-replacement requirement), and the wiring to Operations Manager manual triggers (`legacyWrapper: false`). Companion changes: - helpers/create-json-form-rest-bound.json: new annotated scaffold with a worked Inventory Manager Site/Device cascade example, in the same `_comment_*` style as the existing helpers. - helpers/create-json-form.json: one-line `_comment_bindingSchema` redirecting readers to the new helper when bindingSchema must not be empty. - builder-agent/SKILL.md: the JSON Forms subsection shrinks to a pointer at the new skill so there's no duplicated source of truth; the helpers table at the bottom splits the JSON Form row into static and REST-bound entries and points both at the new skill for full details. Closes itential#36 (was rejected because builder-agent was the wrong home for this content). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
2 participants
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.
Summary
helpers/create-json-form-rest-bound.jsonfor JSON Forms whose dropdowns are populated live from IAP endpoints, including the cascading pattern (one dropdown's URL path parameter fed by another field).builder-agent/SKILL.md: bulkDELETE /json-forms/forms, thestruct↔bindingSchemamirroring requirement, and thevariables[]+DependencyWidgetmechanism that wires cascading dropdowns.Background
While building a Site/Device cascade against Inventory Manager I produced a form whose dropdowns rendered but never fetched. Working from the existing
create-json-form.jsonhelper, I had assumedbindingSchema: {}was always correct and used{customKey}curly-brace interpolation inhref. Both wrong. The user hand-built a working form to demonstrate the actual pattern; this PR captures what was learned so the next agent doesn't repeat the mistakes.Changes
New file:
helpers/create-json-form-rest-bound.json_comment_*style as the other helpersEdits:
.claude/skills/builder-agent/SKILL.mdGET /json-forms/forms/{id}andDELETE /json-forms/forms(bulk; body{"ids":[...]}— there is no per-id DELETE; per-id 404s)struct.type: "array"requirement, thestruct↔bindingSchemamirroring requirement,:namecolon syntax for path params (not{name}), thevariables[]cascade mechanism withreferenceJSON pointers into form data, theDependencyWidgetui:widgetrequirement on both source and dependent fields, andGET /automation-studio/json-forms/method-optionsfor bindable-endpoint discoveryEdit:
helpers/create-json-form.json_comment_bindingSchemaredirecting readers to the new helper whenbindingSchemamust not be emptyTest plan
jq typepasses on both helpers (verified locally)/json-forms/formsagainst a live platform → form appears in Studio with two dropdowns:inventoryIdentifierfilled from/sitereference)🤖 Generated with Claude Code