Provide more clear flask -e, --env-file flag desription #5532
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
differencialx
force-pushed
the
improve-cli-env-file-description
branch
from
5932b84
to
2ed9dd0
Compare
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.
Currently the description for
flaskcli command-e, --env-fileflag is misleading. I understand that this functionality is covered and perfectly explained in docs, but in case you are not familiar with documentation you will just useflask --helpcommand to read which flags are allowed.This PR just adds few sentences to make
-e, --env-fileflag description more clear and exhaustive.Before:
After
Initial PR with for
-e, --env-fileflag: #4646