githubnext / githubnext/ado-aw
Add strict validation for untrusted raw step fragments
- Dominant language
- Rust
- Stars
- 23
- Forks
- 8
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 22
Description
Follow-up extracted from #1061. Raw authored steps can still reach `Step::RawYaml`; add a strict validation path for isolated untrusted fragments using the current typed task parsers and lint findings. Define accepted shapes, reject unsafe or ambiguous input, and add compile/lint contract tests.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how authored steps reach Step::RawYaml and how the current typed task parsers produce lint findings. Define the accepted shapes for isolated untrusted fragments, reject unsafe or ambiguous input, and add compile and lint contract tests that demonstrate the validation boundary and its completed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100