-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
feat: Add GraphQL bulk mutations createMany, updateMany, deleteMany
#10341
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
Open
Moumouls
wants to merge
12
commits into
parse-community:alpha
Choose a base branch
from
Moumouls:moumouls/create-update-delete-many-gql
base: alpha
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1,672
−16
Open
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
70d7baf
feat: create, update, delete many graphql
Moumouls dce171f
fix: lock
Moumouls 7813f36
Merge branch 'upstream/alpha' into moumouls/create-update-delete-many…
Moumouls 4196811
fix: sanitize bulk errors
Moumouls 3cc83d9
fix: ignore duplicate check
Moumouls 8f24cdb
fix: improve error util
Moumouls 8b41f8d
test: cover sanitize errors
Moumouls 9eb43e1
test: duplicate id during delete
Moumouls 030cd15
Merge branch 'alpha' into moumouls/create-update-delete-many-gql
Moumouls 70d9738
Merge branch 'alpha' into moumouls/create-update-delete-many-gql
Moumouls 05ead2f
fix: Sanitize GraphQL bulk limit errors and clone updateMany fields
Moumouls 0e8d9f0
fix: Use const for updateMany fields to satisfy prefer-const
Moumouls File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🌐 Web query:
Jasmine expectAsync toBeRejected toBeRejectedWithError signature arguments💡 Result:
In the Jasmine testing framework, expectAsync is used to create an asynchronous expectation, which returns a promise that must be awaited or returned by the spec [1]. The toBeRejected matcher expects a promise to be rejected, and it takes no arguments [2][3]. The toBeRejectedWithError matcher expects a promise to be rejected with a value that matches the provided parameters [4][5]. It accepts two optional arguments: 1. expected: An Error constructor that the thrown object should be an instance of [4][5]. If this argument is omitted, the default Error constructor is used [4][5]. 2. message: A string or regular expression that the message property of the thrown error must match [4][5]. Example usage: await expectAsync(aPromise).toBeRejectedWithError(MyCustomError, 'Error message'); await expectAsync(aPromise).toBeRejectedWithError(MyCustomError, /Error message/); await expectAsync(aPromise).toBeRejectedWithError(MyCustomError); await expectAsync(aPromise).toBeRejectedWithError('Error message');
Citations:
🏁 Script executed:
Repository: parse-community/parse-server
Length of output: 384
🏁 Script executed:
Repository: parse-community/parse-server
Length of output: 11321
Replace these rejected-message assertions with
toBeRejectedWithError()and await them.toBeRejected()does not accept anexpectedargument, so Jasmine ignores these strings and the assertions would pass even if the controller emitted a different error text. Also invokeawait expectAsync(...)so a non-rejection is reported as a failed spec rather than an unhandled rejection.💚 Proposed fix
Apply the same change to the
updateManyAliasanddeleteManyAliascases.🤖 Prompt for AI Agents