PAIR-code / PAIR-code/deliberate-lab
Add full UI support for enums, arrays, and nested fields in structured output config
Open
Nobody has claimed this yet.
frontend
runtime:experimenter-ux
stale
- Dominant language
- TypeScript
- Stars
- 96
- Forks
- 40
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 20
Description
At time of writing, the structured output UI supports:
- String
- Integer
- Number
- Boolean
- Flat fields only
The backend also supports:
- Enums
- Arrays
- Nested fields
I don't know what will happen if someone defines one of the extra features in a template and tries to open it in the UI.
The UI also doesn't support reordering fields, which would be nice to have.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the structured output UI and its template-loading path, then compare the supported scalar fields with the backend features named in the issue. The work is done when enums, arrays, nested fields, and field reordering work in the UI without breaking existing string, integer, number, or boolean fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100