-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Tag Tests & Updates #2816
Tag Tests & Updates #2816
Conversation
Codecov ReportBase: 40.20% // Head: 41.67% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #2816 +/- ##
==========================================
+ Coverage 40.20% 41.67% +1.46%
==========================================
Files 544 544
Lines 25739 25736 -3
Branches 260 260
==========================================
+ Hits 10349 10726 +377
+ Misses 15350 14970 -380
Partials 40 40
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
b20818a
to
dbbffac
Compare
Thanks for contribute this @kooliokey ! Please leave the PersetColor parameter as the same as Color. This will reduce breaking changes. |
Hi! The changes should not introduce any breaking changes and in fact they fix a bug I found with tag - if you have it set to default color, then to a custom/preset, then back to default color it doesn't style currently. This change set fixed it. I think the only way it would be a breaking change is if someone had the Click "Change Color" With the code in this PR, the final step results in the correct styling as in step 1. |
|
PresetColor
in favor of usingColor
.PresetColor
parameter is nullable but throws if you set it to null and it uses the logic in Color behind the scenes anyway.PresetColor
to discourage future usage and indicate a default value forColor
🤔 This is a ...
🔗 Related issue link
#2644
💡 Background and solution
📝 Changelog
☑️ Self Check before Merge