-
-
Notifications
You must be signed in to change notification settings - Fork 596
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: invalid name for Parse.Role
throws incorrect error
#1481
Conversation
Thanks for opening this pull request!
|
Codecov Report
@@ Coverage Diff @@
## alpha #1481 +/- ##
=======================================
Coverage 99.94% 99.94%
=======================================
Files 61 61
Lines 5949 5954 +5
Branches 1357 1357
=======================================
+ Hits 5946 5951 +5
Misses 3 3
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Ready to merge?
Parse.Role
throws incorrect error
Yep! |
## [3.4.3-alpha.2](3.4.3-alpha.1...3.4.3-alpha.2) (2022-05-29) ### Bug Fixes * invalid name for `Parse.Role` throws incorrect error ([#1481](#1481)) ([8326a6f](8326a6f))
🎉 This change has been released in version 3.4.3-alpha.2 |
🎉 This change has been released in version 3.4.3-beta.1 |
🎉 This change has been released in version 3.4.3 |
## [3.4.3](parse-community/Parse-SDK-JS@3.4.2...3.4.3) (2022-07-02) ### Bug Fixes * creating a Parse.File with base64 string fails for some file types ([parse-community#1467](parse-community#1467)) ([c07d6c9](parse-community@c07d6c9)) * invalid name for `Parse.Role` throws incorrect error ([parse-community#1481](parse-community#1481)) ([8326a6f](parse-community@8326a6f))
New Pull Request Checklist
Issue Description
Creating a role with an invalid name does not throw an error, leaving the API to throw
Error: name is required
Related issue: #1480
Approach
Validate role name on create
TODOs before merging