-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Feature: more intuitive radius (SVG) #23
Conversation
I think it's very unintuitive to have the the radius parameters be an absolute size instead of a percentage, like 60%, 40%, etc. At least for SVGs.
Will have to fix the that action. |
It already gets the pushed commit, and fixes an issue found in #23.
That did the trick |
This makes sense to me :) Thank you. |
4d21394
to
18806bf
Compare
I will wait till enthusiast shares his opinion on this, and also I would like to ask if this should be released to 2.0.0 or 1.1.0, I don't know if this is actually breaking backwards compatibility or not (I mean, it breaks rounded SVGs written before this PR, but is it that huge of a break? I'm trying to follow https://semver.org/). And also the same goes to the SVG class names changes. |
Much better! |
Okay then I will merge this into develop and next release will be 2.0.0. Main breaking changes will be (for the moment):
|
I think it's very unintuitive to have the the radius parameters be an absolute size instead of a percentage, like 60%, 40%, etc. At least for SVGs, where
rx
will always be a value from 0 to 0.4 for modules since it's a vector.I'm not making the commit directly to develop since I want to know what you guys think about this.
Mainly @enthus1ast @EyeCon @tandy-1000