-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flexible SVGO settings for different folders #78
Comments
Hi. It’s related to #41 and I like the idea. Just need to think how we can keep the configuration as simple as possible. |
Well, I think everything should be same as it is now, we just could add one more level of configuration:
And on each level we can redefine something, or add level-specific configuration. On the new |
I’ll try to find time this week to make it possible to use objects in the sourceDirs array (#41), so that you can define directory specific optimization and prefix. |
Cool! Looking forward to it. Ping me if you need any help from a collaborator ;) |
Hi and thanks for an awesome addon. I just wanted to ask if there was an update to this feature request? I suddenly found myself in need of this functionality. |
Yes, please! Run into a similar need, to convert monochrome icons to use |
Hi, @ivanvotti
Great addon you have here 👍 I have a feature request.
I ran into a requirement to have separated SVGO configs for different folders, but then join them into one single file with symbols. Here is an example:
We have two types of icons: monochrome and colored. So, we put them to
app/assets/icons/mono
andapp/assets/icons/colored
respectively. SVG files are stored as they out using Sketch exporting tool. We don’t want to preprocess them with SVGO beforehand and put to the project, since configuration may differ from time to time and for different people, if they use SVGO as a Sketch plugin. That’s why we would rather save sources inapp/assets/icons/
foulders.So, what I’m offering here is to have such a flexible configuration available:
Do you think this is something that could have place in the addon and could be developed soon? I could take care of this if only I was sure that these changes would be something that is wanted to be merged and correspond with your view on this :)
The text was updated successfully, but these errors were encountered: