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
It would be really helpful if you could add a prefix option to each individual sourcePath strings. The would you allow for easier sorting if using different collection and reduce name collisions.
We've also run into the need for this and found it would give a lot of flexibility.
Even more having sourceDirs an array of objects (like suggested above) which supports optimizer and stripPath options individually, would be amazing (though I understand it might be more complicated).
Our use-case is an addon that will need to import some SVG's from an npm module and add it to the host app. With what's currently supported by the addon, we're running into naming conflicts with some other SVG's that are imported directly by our host app, the prefix would solve this issue.
Looking forward for something like this, if I could help in any way, feel free to let me know
It would be really helpful if you could add a prefix option to each individual sourcePath strings. The would you allow for easier sorting if using different collection and reduce name collisions.
Then the generated icons would be:
or if the main prefix option is used:
Then the generated icons would be:
The text was updated successfully, but these errors were encountered: