Style Reference Feature
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Is your feature request related to a problem? Please describe.
Slow down in the changes when changing a style that is copied and pasted in multiple objects.
Describe the solution you'd like
I would like to have a Style Reference in addition to Copy/Paste Style. This would create a pointer logic for styles that automatically change all child styles when the father is changed.
Describe alternatives you've considered
The alternative is to define a new style common to multiple objects.
Additional context
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 named. Start by comparing the requested Style Reference behavior with the existing Copy/Paste Style workflow, then clarify how style pointers are created, maintained, and removed; done should mean changing a referenced style updates all associated objects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100