-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Log a warning in case of a unknown options #8938
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Labels
bounty:$20
Bounty applies for fixing this issue (Parse Bounty Program)
state:released
Released as stable version
state:released-alpha
Released as alpha version
state:released-beta
Released as beta version
type:feature
New feature or improvement of existing feature
Comments
Thanks for opening this issue!
|
4 tasks
@mtrezza Can I try this issue? |
Sure, please go ahead |
4 tasks
Related: #7069 |
🎉 This change has been released in version 7.1.0-alpha.5 |
🎉 This change has been released in version 7.1.0-beta.1 |
🎉 This change has been released in version 7.1.0 |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
bounty:$20
Bounty applies for fixing this issue (Parse Bounty Program)
state:released
Released as stable version
state:released-alpha
Released as alpha version
state:released-beta
Released as beta version
type:feature
New feature or improvement of existing feature
New Feature / Enhancement Checklist
Current Limitation
When we pass a wrong option in Parse config it doesn't make a warning,
Feature / Enhancement Description
There should be a validation or list of giving options to prevent such mistakes with a warning.
Example Use Case
for instance in the Parse config I had a typo like:
masterKeyIPs
which was the correct form wasmasterKeyIps
and it took time to find out why I got error.The text was updated successfully, but these errors were encountered: