Skip to content
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

Fix border-inline-start and border-inline-end not having any valid ordering #1756

Merged
merged 2 commits into from
Dec 11, 2024

Conversation

dddlr
Copy link
Collaborator

@dddlr dddlr commented Dec 11, 2024

What is this change?

Fix how border-inline-start and border-inline-end does not have any valid ordering in the shorthand-property-sorting ESLint rule.

Follow up to #1749

Why are we making this change?

Fix one more false positive that slipped through the cracks.


PR checklist

Don't delete me!

I have...

  • Updated or added applicable tests
  • Updated the documentation in website/

Copy link

changeset-bot bot commented Dec 11, 2024

🦋 Changeset detected

Latest commit: 07385fe

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@compiled/eslint-plugin Patch
@compiled/utils Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

netlify bot commented Dec 11, 2024

Deploy Preview for compiled-css-in-js canceled.

Name Link
🔨 Latest commit 07385fe
🔍 Latest deploy log https://app.netlify.com/sites/compiled-css-in-js/deploys/6759263283cd3100084d426c

@dddlr dddlr force-pushed the bug/border-inline-start-sorting branch from 06f59c3 to 99e4aec Compare December 11, 2024 05:37
package.json Outdated
@@ -158,5 +158,6 @@
"react"
]
}
]
],
"packageManager": "yarn@1.22.21+sha256.dbed5b7e10c552ba0e1a545c948d5473bc6c5a28ce22a8fd27e493e3e5eb6370"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's this about?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gahhh yarn keeps adding that

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we're supposed to specify what version of yarn the repo should use through packageManager

i never got the chance to set this up properly, so it keeps trying to add it whenever i run yarn install

maybe i should just set it up 🤔 hold on

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm looks a bit complicated, something for another day...

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah no clue 🫡

Copy link
Collaborator

@kylorhall-atlassian kylorhall-atlassian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fair—worst-case it's an edge-case for us we might want to handle better one day, but for now it's perfectly acceptable.

@dddlr dddlr merged commit 6fb2894 into master Dec 11, 2024
13 checks passed
@dddlr dddlr deleted the bug/border-inline-start-sorting branch December 11, 2024 22:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants