Closed six7 closed 3 months ago
Latest commit: 92732eff8c016a59ce17a89d14eb085e3abcc1c8
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
Closes #2907
With 2.0 we seem to have introduced a regression when it comes to the order of token keys. We made it so that
type
always comes first, thenvalue
, and so on. This is bad because we need to respect users key ordering.With this PR we're now respecting the order and keeping it the same by not destructuring the object.
Before
As you can see in this screenshot we reordered keys, even though the user didnt specify that.
After
Here's me after the change just adding a modifier - note how it preserves the order of
value
first.