Tailwind Debug Borders: A Simple Solution for Smarter Debugging #14281
NicolasSoroka
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Sure, we all do this on a daily basis, but why is there still no class to identify an element? I'm talking, of course, about the one and only
✨
1px solid red
✨When we are debugging multiple elements at the same time, we need different colors and, in the end, have to delete all the border and border-color classes that we added... a little bit annoying.
So, a new class like
debug-red
ordebug-[#22d3ee]
to identify the debugging ones from the actual useful borders would apply:So... is this really necessary??? You may be thinking...
Well, it's just an improvement. I find myself using these classes a lot, and having this custom solution works really well. Also, this new class can be removed by a linter.
Let me know what you think!
Beta Was this translation helpful? Give feedback.
All reactions