Move custom cloud provider config warnings higher #2278
Merged
Conversation
This file contains hidden or 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
derrickmehaffy
added
pr: fix
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Member
Author
|
There was also a small fix to let node 20 work properly too |
pwizla
added
the
temp - port to docs-next
pwizla
removed
the
temp - port to docs-next
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What does it do?
Moves and slightly alters the configuration file warnings higher so that users actually see them (we get a lot of tickets about this)
Why is it needed?
Generating a lot of tickets since users aren't seeing the warning and aren't using the environment config
Related issue(s)/PR(s)
N/A