Support defining presets as functions #2680
Merged
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.
Description by @adamwathan
This PR adds support for defining presets as functions in case users need to accept options in their presets. We don't actually provide anything to these functions, we just notice if you've given us a function and invoke it with no arguments on your behalf. This lets your preset be used like this:
We need this internally for the Tailwind UI plugin which we're currently converting to a preset for Tailwind 2.0.