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
In v3, the default extractor gets passed in an object that gives it access to the user's prefix and separator config options. Custom extractors don't have access to these options even though they seem helpful for extraction logic. Was there a reason for this difference? Thanks!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In v3, the default extractor gets passed in an object that gives it access to the user's
prefix
andseparator
config options. Custom extractors don't have access to these options even though they seem helpful for extraction logic. Was there a reason for this difference? Thanks!(For context: I maintain a plugin that uses a custom extractor, but this limitation requires the user to pass in any prefix into the extractor separately https://fluid.tw/#custom-tailwind-prefix-andor-separator)
Beta Was this translation helpful? Give feedback.
All reactions