feat: add more convenience QueryConstraint's for handling ParseObjects #298
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.
New Pull Request Checklist
Issue Description
For particular
QueryConstraint
's such as:!=
,containedIn
,notContainedIn
,containedBy
,containsAll
, the developer has to convertParseObject
's toPointer<ParseObject>
's to properly use constraint.Related issue: #n/a
Approach
Add convenience methods to convert the
ParseObject
's toPointer<ParseObject>
's for the developer, throws errors if the object can't be converted.TODOs before merging
QueryConstraint
's to their own file. MoveQueryWhere
to it's own file