Make rings configurable #150
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey 👋
I've made the changes needed to make rings disableable (is that a word?) since it's been super annoying to just slap
focus:ring-0
onto every<input>
since I generally don't use rings in my applications. They're also super annoying to override, for example with checkboxes where it isn't possible to get rid of this behaviour at all (addingfocus:outline-none focus:ring-0
to my checkbox doesn't seem to do anything except make the outline white instead of non-existant).This is an optional flag that can be passed to the plugin initialize function. This makes sure that people updating their packages won't get a surprise when their rings stop existing.
This is related to tailwindlabs/tailwindcss#12143.