[feature request] Allow aliasing entire collection
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by locating the existing support for aliasing individual icons and compare it with the TypeScript example in the issue. Determine where collection-level aliasing belongs and verify that a collection alias makes its icons available under the new prefix without manually generating per-icon aliases.
Written by the indexing model from the issue text.
Description
It would be nice if you could alias and entire collection instead of just an icon.
Right now I do it this way.
const createIconAliases = (newPrefix: string, iconifyJson: IconifyJSON) => {
const exisitngPrefix = iconifyJson.prefix;
const icons = Object.keys(iconifyJson.icons);
return icons.reduce(
(object, value) => {
object[`${newPrefix}:${value}`] = `${exisitngPrefix}:${value}`;
return object;
},
{} as Record<string, string>,
);
};
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 97
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from nuxt/icon
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Allow separate providers for SSR and client (`provider: { server, client }`)Possibly taken @pont1s claimed this 25 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Remote server bundle duplicates concurrent collection downloadsPossibly taken @onmax claimed this 48 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
cursor/community-plugins#465 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
vetro-protocol/vetro-monorepo#978 ·
Maintainers usually reply within 1 day
-
ai-generated bug category:security effort:s priority:p3
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
LanternOps/breeze#9697 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
maniator/verticopolis#1303 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
components-web-app/docs#297 ·