Upgrade deprecated order-none
to order-0
#18126
Merged
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.
This PR adds an initial version for deprecated utilities. Right now it's hardcoded to just the
order-none
utility.This means that
order-0
andorder-[0]
will not be migrated toorder-none
anymore. We did that automatically because we prefer named utilities over bare values and arbitrary values.With this PR,
order-none
is ignored.Similarly,
order-none
will be migrated toorder-0
instead (defined in a separate migration for deprecated values). Made it a new migration instead of using the legacy migration because there all utilities still exist, but are defined differently (e.g.:shadow
,shadow-sm
,shadow-xs
).This PR is also an initial version, it doesn't add any form of
deprecated
flag or feature on a per-utility implementation basis. This therefor has the side effect that if you have a customorder-none
defined, that it will also be ignored during migrations.Test plan
order-0
is not migrated toorder-none
order-none
is migrated toorder-0
(if it's safe to do so, the signature is still computed to ensure the output is the same).order-0
is not migrated toorder-none
and thatorder-none
is migrated toorder-0
.