-
-
Notifications
You must be signed in to change notification settings - Fork 598
docs: Fix incorrect type in docs for Parse.Query.containedIn
and Parse.Query.notContainedIn
#1784
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
Conversation
Fixes parse-community#1783 Signed-off-by: Richard Groves <[email protected]>
Thanks for opening this pull request! |
I'm not sure which bit of the template I didn't use, AFAICS I filled in each section. |
All good, I removed the "Fixes #1783" at the top, that's what the "Closes:" is for. And there's a bug in the bot I guess because this is a new template, let me fix that real quick... |
ParseQuery.containedIn
and ParseQuery.notContainedIn
ParseQuery.containedIn
and ParseQuery.notContainedIn
ParseQuery.containedIn
and ParseQuery.notContainedIn
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.
The tests fail because in JSDos it's Array
. It may be more correct to specify the exact types that can be passed, unless really any type can be passed, including objects, array, etc.
Array<null|undefined|String|Number|Boolean>
is just a guess
Better type def in doc Co-authored-by: Manuel <[email protected]> Signed-off-by: Richard Groves <[email protected]>
Better type def in doc Co-authored-by: Manuel <[email protected]> Signed-off-by: Richard Groves <[email protected]>
I'm not 100% sure what types can be in the array, and whether an array of items has to be of a single type or can have mixed contents. Would specifying the type list limit it to an array of homogenous types? I know I have arrays of objects (or object pointers internally) so 'object' would have to be in the list of allowed types. |
Yes. So let's go with |
ParseQuery.containedIn
and ParseQuery.notContainedIn
Parse.Query.containedIn
and Parse.Query.notContainedIn
Codecov ReportBase: 99.90% // Head: 99.90% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## alpha #1784 +/- ##
=======================================
Coverage 99.90% 99.90%
=======================================
Files 61 61
Lines 6103 6103
Branches 1482 1482
=======================================
Hits 6097 6097
Misses 6 6
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View 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!
🎉 This change has been released in version 4.1.0-beta.1 |
🎉 This change has been released in version 4.1.0-alpha.1 |
🎉 This change has been released in version 4.1.0 |
Pull Request
Issue
Closes: #1783
Approach
Documentation and method parameter type updated for
Parse.Query.containedIn
andParse.Query.notContainedIn
Tasks