chuckdries
commented
2 years ago Hm, I think the className stuff must be a vscode extension on your end because it doesn't happen for me. Regardless, it doesn't actually affect anything so no worries
Closed jayeclark closed 2 years ago
chuckdries
commented
2 years ago Hm, I think the className stuff must be a vscode extension on your end because it doesn't happen for me. Regardless, it doesn't actually affect anything so no worries
jayeclark
commented
2 years ago Yep, I found it --- a repository I'd worked on recently had some recommended VSCode extensions that I'd auto-installed without looking too closely at them, and one of them was an opinionated sorter for Tailwind classes. Definitely turning that one off! 😆
Signed-off-by: Jay Clark jay@jayeclark.dev
Fixes #11
Hi there! I came across this issue and noticed some minor changes that could help with screen reader accessibility.
VSCode is also forcing some changes to the classnames order every time that I try to save (I assume its a linting setting on the repository?) - the changes to classname order are not related to accessibility.