docs: exhibit defineConfig #4343
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Shinigami92
added
documentation
patak-dev
reviewed
Jul 21, 2021
Shinigami92
force-pushed
the
exhibit-define-config
branch
from
e2f067f to
75eb673
Compare
|
@antfu Would you like to review this? |
antfu
approved these changes
Jul 27, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
I see more and more folks using just
export default () = {...}and then saying that the config cannot handle this and that.Worst case example: #4300 (reply in thread)
This can be prevented by that we exhibit
defineConfigmore in the docs, cause some lazy folks just copy paste and take docs as best practice.Additional context
What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123).