Add configuration for SVG optimization tools#92
Open
mataha wants to merge 1 commit intoSublimeText:developfrom
Open
Add configuration for SVG optimization tools#92mataha wants to merge 1 commit intoSublimeText:developfrom
mataha wants to merge 1 commit intoSublimeText:developfrom
Conversation
deathaxe
force-pushed
the
develop
branch
2 times, most recently
from
794003e to
94e4057
Compare
deathaxe
force-pushed
the
develop
branch
3 times, most recently
from
8483e63 to
4cea400
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I don't expect this to get merged, but I'd rather put it on a public display than not...
Configuration for svglint and svgo - SVG linter and optimizer, respectively - that I use to prepare images before building either directly using
npxor with Inkscape, and which I'd imagine would be useful as a pre-commit hook in the future, should there be such plans.This is not an attempt to turn this package into a JavaScript repo; as a certain developer once said, "I'm going to lose my shit if somebody suggests adding a package.json".