adobe / adobe/spectrum-design-data
RFC #735: SDK `--spec-version` flag behavior
- Dominant language
- Rust
- Stars
- 153
- Forks
- 35
- Avg merge
- 7h 54m
- Merged PRs (30d)
- 111
Description
## Context
Open question from RFC #735 (Spec Versioning and Evolution), tracked in `docs/rfc-coordination.md`.
Define the semantics of a `--spec-version` flag on CLI validation commands: which rule set is active for a given spec version, how dual-format coexistence windows map to rule severity, and whether older spec versions are permanently supported or have a deprecation timeline.
## References
- RFC #735: https://github.com/adobe/spectrum-design-data/discussions/735
- `docs/rfc-coordination.md` RFC #735 row
- `spec/evolution.md`
Contributor guide
Research direction
Start by reading docs/rfc-coordination.md and spec/evolution.md, then review RFC #735 in the linked discussion. Define and document how --spec-version selects rule sets, maps dual-format windows to severity, and handles support or deprecation; done means the open questions have an agreed specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100