You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Sorting the classes of the entire workspace and sorting the classes of a single file (either format on save or command) result in different outcome.
To Reproduce
Steps to reproduce the behavior:
Open command palette and sort entire workspace
Check files for any changes. A small number of our components are now changed.
For example, the classes of our button component gets sorted Original:class="inline-flex items-center tracking-wider transition border border-transparent rounded-lg focus:outline-none focus:ring disabled:opacity-25" Change:class="inline-flex items-center tracking-wider border border-transparent rounded-lg transition focus:outline-none focus:ring disabled:opacity-25"
Now either format on save or use the other command
The file has been sorted again and is back to the original Original:class="inline-flex items-center tracking-wider transition border border-transparent rounded-lg focus:outline-none focus:ring disabled:opacity-25"
The button is no longer marked as changed
Other example: Format entire workspace: <div class="py-1 mb-2 text-xs font-bold rounded grid grid-cols-12 bg-grey-300 gap-x-4 text-grey-700" > Format on save: <div class="grid grid-cols-12 py-1 mb-2 text-xs font-bold rounded bg-grey-300 gap-x-4 text-grey-700" >
Expected behavior
Both ways of sorting behave the same and do not cancel each other out.
Screenshots
I removed all code from our button but the following and the problem still occurs
Format entire workspace:
... and many more
Format on save:
All files will be reverted to the original.
Desktop (please complete the following information):
OS: macOS Monterey 12.1
Browser: Chrome
Version 96.0.4664.110 (Official Build) (x86_64)
The text was updated successfully, but these errors were encountered:
I believe this is a known issue. The packaged version of Rustywind is v0.7.1, but Headwind's own implementation matches the behavior of Rustywind v0.6.7 (which I found out the hard way: by testing them all.)
I've manually installed Rustywind v0.6.7 and use it from the command line instead of relying on the one shipped with Headwind.
Describe the bug
Sorting the classes of the entire workspace and sorting the classes of a single file (either
format on save
or command) result in different outcome.To Reproduce
Steps to reproduce the behavior:
Original:
class="inline-flex items-center tracking-wider transition border border-transparent rounded-lg focus:outline-none focus:ring disabled:opacity-25"
Change:
class="inline-flex items-center tracking-wider border border-transparent rounded-lg transition focus:outline-none focus:ring disabled:opacity-25"
Original:
class="inline-flex items-center tracking-wider transition border border-transparent rounded-lg focus:outline-none focus:ring disabled:opacity-25"
Other example:
Format entire workspace:
<div class="py-1 mb-2 text-xs font-bold rounded grid grid-cols-12 bg-grey-300 gap-x-4 text-grey-700" >
Format on save:
<div class="grid grid-cols-12 py-1 mb-2 text-xs font-bold rounded bg-grey-300 gap-x-4 text-grey-700" >
Expected behavior
Both ways of sorting behave the same and do not cancel each other out.
Screenshots
I removed all code from our button but the following and the problem still occurs
Format entire workspace:
... and many more
Format on save:
All files will be reverted to the original.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: