malliaridis / malliaridis/penpot-plugin-material-theme-builder
Provide library name for identified themes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
### Description
When the user has multiple libraries in a file and the themes are named the same, they are merged together and not distinguished in the plugin.
To avoid an invalid merge of themes and to make it clearer from which library a speicific theme is coming, themes and its assets should have a reference to the library they are originated from.
### Acceptance Criteria
- Themes from different libraries with the same name are no longer merged together
- It is clear in theme selections from which library a theme is coming from
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 tracing how themes and their assets are identified, merged, and presented in theme selections. Done means same-named themes from different libraries remain separate and each theme clearly identifies its source library.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100