Closed pretzelhammer closed 2 years ago
Deployed Styleguide and Lab.Notes
File | Before | After |
---|---|---|
components/Button/script.js |
5.5 kB |
-0.34%↓5.5 kB |
components/Button/styles.css |
5.2 kB |
0.06%↑5.2 kB |
components/Calendar/script.js |
7.4 kB |
-0.08%↓7.4 kB |
components/Calendar/styles.css |
2.1 kB |
0.1%↑2.1 kB |
components/PinInput/script.js |
5.8 kB |
-0.07%↓5.8 kB |
components/Stepper/script.js |
5.7 kB |
-0.11%↓5.7 kB |
components/Theme/script.js |
15.9 kB |
0.7%↑16.0 kB |
utils/maker-colors.js |
3.1 kB |
23%↑3.8 kB |
Total (Includes all files) | 1.7 MB |
0.2%↑1.7 MB |
Tarball size | 324.5 kB |
0.2%↑325.3 kB |
🤖 This report was automatically generated by pkg-size-action
Deployed Styleguide and Lab.Notes
:tada: This PR is included in version 15.0.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
This PR is an aggregate of the following PRs:
Migration Guide: 14.x -> 15.x
Breaking changes that LIKELY affect your app
(1) MButton pattern & variant renames
MButton patterns
primary
,secondary
, andtertiary
have been removed since they're identical to variantsfill
,outline
, andghost
respectively. MButton variantsprimary
,secondary
, andtertiary
have also been renamed tofill
,outline
, andghost
respectively. Filled button patternsprimaryFilled
,errorFilled
,successFilled
,warningFilled
,infoFilled
have been renamed toprimaryFill
,errorFill
,successFill
,warningFill
,infoFill
. Migration refactor table of examples:<m-button>
<m-button>
(no changes)<m-button variant="primary">
<m-button variant="fill">
<m-button variant="secondary">
<m-button variant="outline">
<m-button variant="tertiary">
<m-button variant="ghost">
<m-button pattern="primary">
**<m-button variant="fill">
<m-button pattern="secondary">
**<m-button variant="outline">
<m-button pattern="tertiary">
**<m-button variant="ghost">
<m-button pattern="primaryFilled">
<m-button pattern="primaryFill">
<m-button pattern="errorFilled">
<m-button pattern="errorFill">
<m-button pattern="successFilled">
<m-button pattern="successFill">
<m-button pattern="warningFilled">
<m-button pattern="warningFill">
<m-button pattern="infoFilled">
<m-button pattern="infoFill">
Note:** If you were using these deprecated patterns in a custom theme and wish to continue using them, you can update them from this:
To this:
(2) MNotice prop rename
MNotice's
variant
prop has been renamed todisplay
. Migration refactor table of examples:<m-notice>
<m-notice>
(no changes)<m-notice variant="inline">
<m-notice display="inline">
<m-notice variant="block">
<m-notice display="block">
Breaking changes that LIKELY DO NOT affect your app
(3) Default theme changes
NOTE: If you're using MTheme at the root of your app and setting an explicit primary color then these changes won't affect your app. These changes only affect people who are using Maker without MTheme or with MTheme but aren't setting an explicit primary color and have been relying on the implicit primary color being
#000000
.Within the default theme the primary color has changed from
#000000
to#006aff
, the derived contextual primary colors have been updated, the overlay color has changed fromrgba(0, 0, 0, 0.3)
torgba(0, 0, 0, 0.32)
. The default parameters within themaker-colors
utility function have also been updated accordingly.If you weren't using MTheme before and relying on the implicit primary color being
#000000
, e.g.You will now have to import MTheme and explicitly set the primary color to
#000000
, e.g.Also, if you were previously using the
maker-colors
utility function and relying on the implicit primary color being#000000
by calling the function with only the first parameter, e.g.makerColors(bgColor)
, then you now also have to pass#000000
as an explicit 2nd argument to maintain the same appearance in your app migrating to 15.x from 14.x, e.g.makerColors(bgColor, '#000000')
. Again, if you were already using the utility function with an explicit 2nd parameter in 14.x,makerColors(bgColor, primaryColor)
, then you do not have to make any changes when migrating to 15.x.