You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:
Current behavior
I have come across a conflict related to registering icons that share the same name but have different paths, such as "arrowUp" from the "solid" and "outline" directories. The issue arises when the registration process checks if the name already exists.
register(icons: SvgIconType | SvgIconType[]) {
for (const { name, data } of Array.isArray(icons) ? icons : [icons]) {
if (!this.svgMap.has(name)) {
this.svgMap.set(**name**, new SvgIcon(data));
}
}
}
Expected behavior
should be able to handle icons with the same name but different paths in a way that allows both versions to coexist. Resolution Suggestions:
add the possibility to add prefix / postfix to icon output name when generation
Minimal reproduction of the problem with instructions
Register icons with the same name but different paths, such as "arrowUp" from both the "solid" and "outline" directories.
What is the motivation / use case for changing the behavior?
Environment
Angular version: X.Y.Z
Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: XX
- Platform:
Mac
Others:
The text was updated successfully, but these errors were encountered:
I'm submitting a...
Current behavior
I have come across a conflict related to registering icons that share the same name but have different paths, such as "arrowUp" from the "solid" and "outline" directories. The issue arises when the registration process checks if the name already exists.
Expected behavior
should be able to handle icons with the same name but different paths in a way that allows both versions to coexist.
Resolution Suggestions:
add the possibility to add prefix / postfix to icon output name when generation
will be
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Environment
The text was updated successfully, but these errors were encountered: