Support managing trait/option availability across variants from the trait itself
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 2h 52m
- Merged PRs (30d)
- 85
Description
Summary
Currently, when adding a new trait or trait option, you have to individually visit each variant to enable it. This is tedious, especially for registries with many variants. We should support a two-way experience where you can also manage variant availability directly from the trait or trait option.
Current Behavior
- Create a new trait or trait option.
- Navigate to each variant individually.
- Enable the trait/option on each variant one by one.
This is repetitive and error-prone, especially as the number of variants grows.
Desired Behavior
- When viewing/editing a trait or trait option, provide easy access to control which variants it is available on.
- This could be a checklist of variants, a bulk toggle, or similar UI that lets you enable/disable the trait across all variants in one place.
- The existing per-variant configuration should continue to work as well (two-way management).
Benefits
- Dramatically reduces the number of clicks needed when adding new traits or options.
- Reduces the chance of forgetting to enable a trait on a specific variant.
- Makes the admin experience much smoother for registries with many variants.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are identified. Start by locating the trait, trait-option, and variant admin screens and their existing per-variant availability flow; define the two-way behavior and verify that changes made from either screen stay consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100