Parse Server for Node.js / Express
APACHE-2.0 License
Bot releases are visible (Hide)
Published by parseplatformorg 5 months ago
Published by parseplatformorg 5 months ago
Published by parseplatformorg 5 months ago
Published by parseplatformorg 6 months ago
Published by parseplatformorg 7 months ago
Published by parseplatformorg 7 months ago
Published by parseplatformorg 7 months ago
Published by parseplatformorg 7 months ago
Published by parseplatformorg 7 months ago
Required
option not handled correctly for special fields (File, GeoPoint, Polygon) on GraphQL API mutations (#8915) (907ad42)Published by parseplatformorg 7 months ago
Published by parseplatformorg 7 months ago
Published by parseplatformorg 7 months ago
verifyUserEmails
, preventLoginWithUnverifiedEmail
set to functions (#8838) (8e7a6b1)beforeFind
when using Parse.Query.include
(#8765) (7d32d89)masterKeyIps
regardless of ACL and CLP (#8957) (a7b5b38)verifyEmail
function if both username and email are changed (#8889) (1eb95ae)emailVerifyTokenReuseIfValid: true
generates new token on every email verification request (#8885) (0023ce4)fileExtensions
default value rejects file extensions that are less than 3 or more than 4 characters long (#8699) (2760381)fileUpload.fileExtensions
fails to determine file extension if filename contains multiple dots (#8754) (3d6d50e)Parse.Pointer
in the request body (#8784) (66e3603)undefined
in email verification link on email change (#8887) (e315c13)$setOnInsert
operator to Parse.Server.database.update
(#8791) (f630a45)installationId
to arguments for verifyUserEmails
, preventLoginWithUnverifiedEmail
(#8836) (a22dbe1)installationId
, ip
, resendRequest
to arguments passed to verifyUserEmails
on verification email request (#8873) (8adcbee)Parse.User
as function parameter to Parse Server options verifyUserEmails
, preventLoginWithUnverifiedEmail
on login (#8850) (972f630)enableCollationCaseComparison
, transformEmailToLowercase
, transformUsernameToLowercase
(#8805) (09fbeeb)beforeLogin
and afterLogin
(#8724) (a9c34ef)ignoreEmailVerification
(#8895) (633a9d2)Parse.Session.current
on expired session token instead of throwing error (#8722) (f9dde4a)createdAt
and updatedAt
during Parse.Object
creation with maintenance key (#8696) (77bbfb3)allowClientClassCreation
defaults to false
(#8849) (29624e0)allowExpiredAuthDataToken
defaults to false
(#8860) (e29845f)fields
option is renamed to keys
(#8852) (38983e8)allowClientClassCreation
defaults to false
. (29624e0)masterKeyIps
, even if the request does not require the master key permission, for example for a public object in a public class class. (a7b5b38)auth.<provider>.enabled: true
(0cf58eb)allowExpiredAuthDataToken
defaults to false
; a 3rd party authentication token will be validated every time the user tries to log in and the login will fail if the token has expired; the effect of this change may differ for different authentication adapters, depending on the token lifetime and the token refresh logic of the adapter (e29845f)fields
option is renamed to keys
; this requires updating Parse client SDKs to make the feature compatible with Parse Server 7 (38983e8)Parse.Cloud.beforeDeleteFile'
has been changed to Parse.Cloud.beforeDelete(Parse.File, (request) => {})'
(4e6a375)Parse.User
passed as argument if verifyUserEmails
is set to a function is renamed from user
to object
for consistency with invocations of verifyUserEmails
on signup or login; the user object is not a plain JavaScript object anymore but an instance of Parse.User
(8adcbee)Parse.Session.current()
no longer throws an error if the session token is expired, but instead returns the session token with its expiration date to allow checking its validity (f9dde4a)Parse.Query
no longer supports the BSON type code
; although this feature was never officially documented, its removal is announced as a breaking change to protect deployments where it might be in use. (3de8494)Published by parseplatformorg 7 months ago
verifyUserEmails
, preventLoginWithUnverifiedEmail
set to functions (#8838) (8e7a6b1)masterKeyIps
regardless of ACL and CLP (#8957) (a7b5b38)verifyEmail
function if both username and email are changed (#8889) (1eb95ae)emailVerifyTokenReuseIfValid: true
generates new token on every email verification request (#8885) (0023ce4)fileExtensions
default value rejects file extensions that are less than 3 or more than 4 characters long (#8699) (2760381)Parse.Pointer
in the request body (#8784) (66e3603)undefined
in email verification link on email change (#8887) (e315c13)installationId
to arguments for verifyUserEmails
, preventLoginWithUnverifiedEmail
(#8836) (a22dbe1)installationId
, ip
, resendRequest
to arguments passed to verifyUserEmails
on verification email request (#8873) (8adcbee)Parse.User
as function parameter to Parse Server options verifyUserEmails
, preventLoginWithUnverifiedEmail
on login (#8850) (972f630)ignoreEmailVerification
(#8895) (633a9d2)Parse.Session.current
on expired session token instead of throwing error (#8722) (f9dde4a)allowClientClassCreation
defaults to false
(#8849) (29624e0)allowExpiredAuthDataToken
defaults to false
(#8860) (e29845f)fields
option is renamed to keys
(#8852) (38983e8)allowClientClassCreation
defaults to false
. (29624e0)masterKeyIps
, even if the request does not require the master key permission, for example for a public object in a public class class. (a7b5b38)auth.<provider>.enabled: true
(0cf58eb)allowExpiredAuthDataToken
defaults to false
; a 3rd party authentication token will be validated every time the user tries to log in and the login will fail if the token has expired; the effect of this change may differ for different authentication adapters, depending on the token lifetime and the token refresh logic of the adapter (e29845f)fields
option is renamed to keys
(38983e8)Parse.Cloud.beforeDeleteFile'
has been changed to Parse.Cloud.beforeDelete(Parse.File, (request) => {})'
(4e6a375)Parse.User
passed as argument if verifyUserEmails
is set to a function is renamed from user
to object
for consistency with invocations of verifyUserEmails
on signup or login; the user object is not a plain JavaScript object anymore but an instance of Parse.User
(8adcbee)Parse.Session.current()
no longer throws an error if the session token is expired, but instead returns the session token with its expiration date to allow checking its validity (f9dde4a)Parse.Query
no longer supports the BSON type code
; although this feature was never officially documented, its removal is announced as a breaking change to protect deployments where it might be in use. (3de8494)Published by parseplatformorg 7 months ago
Published by parseplatformorg 7 months ago
Published by parseplatformorg 7 months ago
Published by parseplatformorg 7 months ago