-
-
Notifications
You must be signed in to change notification settings - Fork 598
Error when passing null
as Parse.Cloud.run
option
#2622
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
Labels
type:bug
Impaired feature or lacking behavior that is likely assumed
Comments
🚀 Thanks for opening this issue! ℹ️ You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing. |
A fix should be fairly easy, do you want to give it a try and open a PR? |
null
as Parse.Cloud.run
option
Yes. I have a branch I can push later today. |
modime
pushed a commit
to modime/Parse-SDK-JS
that referenced
this issue
May 24, 2025
2 tasks
modime
pushed a commit
to modime/Parse-SDK-JS
that referenced
this issue
Jun 2, 2025
mtrezza
pushed a commit
that referenced
this issue
Jun 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
New Issue Checklist
Issue Description
This bug was first found in https://github.com/parse-community/parse-server/ (see issue parse-community/parse-server#9766)
In
_getRequestOptions
in fileParseObject.js
the parameteroptions
is set to{}
if it has no value. This works for values like''
,undefined
or if it is empty, but if it isnull
the code breaks.Steps to reproduce
Call the function
Parse.Cloud.run(<name>, data, null);
or_ParseObject.default._getRequestOptions(null);
directly.Actual Outcome
Error:
Expected Outcome
When no options
_getRequestOptions
should return{}
Some kind of null check for the parameter
options
.Environment
I have tested this in
8.2.0
and8.2.1-alpha.2
. Error occurs in both.The function does not exists in
7.5.2
Server
8.2.0
macOS 15.5
local
Database
MongoDB
macOS 15.5
local
Client
Node
22.14.0
Client
6.1.0
The text was updated successfully, but these errors were encountered: