refactor: remove is-svg #1034
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,5 @@ | ||
| import valueParser from 'postcss-value-parser'; | ||
| import { optimize } from 'svgo'; | ||
| import { encode, decode } from './lib/url'; | ||
|
|
||
| const PLUGIN = 'postcss-svgo'; | ||
|
|
@@ -48,14 +47,13 @@ function minify(decl, opts) { | |
| } | ||
| } | ||
|
|
||
| let result; | ||
| try { | ||
| result = optimize(svg, opts); | ||
| if (result.error) { | ||
| if (result.error.startsWith('Error in parsing SVG')) { | ||
|
There was a problem hiding this comment. I could not find a better way to detect the cause of the error. Maybe @TrySound has got a better suggestion? Anyway I wonder whether it makes sense to throw an error just because we cannot process sommething, instead of just leaving it alone. See this comment #910 (comment) There was a problem hiding this comment. I think we don't need throw the error in this cases (and all cases, for example There was a problem hiding this comment. Doesn't postcss have There was a problem hiding this comment. oh, yep, forgot about it |
||
| return; | ||
| } | ||
| throw new Error(`${PLUGIN}: ${result.error}`); | ||
| } | ||
| } catch (error) { | ||
|
|
||
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have changed these tests because I 've realized there is no meaningful difference between these cases. They're all invalid SVGs. They were handled separately because some failed at the
isSvgstage and some at thesvgostage.