Objective
Add string shortcut support for permissions in included files to match the UX of main workflows.
Context
Priority: HIGH
Category: UX Consistency / Feature Parity
Currently:
- Main Schema: Supports both string shortcuts (
"read-all", "write-all", "read", "write") and object form
- Included Schema: Only supports object form
This creates an inconsistent UX where users must use verbose object syntax in included files even for simple cases.
Approach
- Open
pkg/parser/schemas/included_file_schema.json
- Locate the
permissions field definition
- Change from single type to
oneOf array with two options:
- String enum:
["read-all", "write-all", "read", "write"]
- Object form (existing definition)
- Match the structure from
main_workflow_schema.json permissions.oneOf
- Rebuild binary with
make build
- Test with included files using string shortcuts
Files to Modify
- Update:
pkg/parser/schemas/included_file_schema.json
- Change permissions from object-only to oneOf[string enum, object]
- Add string shortcuts:
read-all, write-all, read, write
Example
After this change, users should be able to write:
# included-security.md
---
permissions: read-all
---
Instead of being forced to use:
---
permissions:
contents: read
issues: read
# ... 13 more properties
---
Acceptance Criteria
Testing
Create test included file:
---
permissions: read-all
---
Compile and verify no validation errors.
AI generated by Planning Assistant
Related to #7944
AI generated by Plan Command for discussion #7935
Objective
Add string shortcut support for permissions in included files to match the UX of main workflows.
Context
Priority: HIGH
Category: UX Consistency / Feature Parity
Currently:
"read-all","write-all","read","write") and object formThis creates an inconsistent UX where users must use verbose object syntax in included files even for simple cases.
Approach
pkg/parser/schemas/included_file_schema.jsonpermissionsfield definitiononeOfarray with two options:["read-all", "write-all", "read", "write"]main_workflow_schema.jsonpermissions.oneOfmake buildFiles to Modify
pkg/parser/schemas/included_file_schema.jsonread-all,write-all,read,writeExample
After this change, users should be able to write:
Instead of being forced to use:
Acceptance Criteria
read-all,write-all,read,writeTesting
Create test included file:
Compile and verify no validation errors.