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

not sorting when using arbitrary value classes #200

Closed
sina-salahshour opened this issue Apr 29, 2023 · 4 comments
Closed

not sorting when using arbitrary value classes #200

sina-salahshour opened this issue Apr 29, 2023 · 4 comments

Comments

@sina-salahshour
Copy link

sina-salahshour commented Apr 29, 2023

Describe the bug
When class names include some arbitrary value class, they are not being sorted.

To Reproduce
Steps to reproduce the behavior:

  1. create a svelte project
  2. add a class like w-[41px]
  3. try to sort by either format/saving or extension sort command.

Expected behavior
classes to be sorted

example

// cell.svelte
<script lnag="ts">
	let enabled = false;
</script>

<button
	class="w-4 bg-black data-[active=true]:bg-white h-4"
	data-active={enabled}
	on:click={() => {
		enabled = !enabled;
	}}
/>

when i remove the data-[active=true]:bg-white class, it works.

Desktop (please complete the following information):

  • OS: Fedora Linux 37
@james0r
Copy link

james0r commented May 6, 2023

This could be confused with what Headwind calls a custom class: a class that you create for your own styling or otherwise versus w-[41px] which would be a Tailwind arbitrary value class.

@sina-salahshour
Copy link
Author

This could be confused with what Headwind calls a custom class: a class that you create for your own styling or otherwise versus w-[41px] which would be a Tailwind arbitrary value class.

ok then let me edit my issue

@sina-salahshour sina-salahshour changed the title not sorting when using custom classes not sorting when using arbitrary value classes May 6, 2023
@arthurmchr
Copy link

Same as #183

@sina-salahshour
Copy link
Author

Same as #183

So I'm closing this issue in favor of #183

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

No branches or pull requests

3 participants