-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
fix: adding internal class (e.g. _User
) fails due to prefixed underscore
#2036
Merged
Conversation
This file contains 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
SpecialClasses from /lib/Constants.js already have the '_' prefix, so adding it will send a double underscore to the Parse server (e.g.: '__Installation' instead of '_installation'), which resolves in an Invalid classname error, based on the SchemaController's function 'validateNewClass'
Thanks for opening this pull request!
|
mtrezza
changed the title
fix: avoid error on SpecialClasses creation
fix: adding internal class (e.g. Feb 10, 2022
_User
) fails due to prefixed underscore
@KodeDave Kindly let me know when this is ready for review. |
mtrezza
approved these changes
Feb 10, 2022
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! Thanks for the fix!
4 tasks
4 tasks
parseplatformorg
pushed a commit
that referenced
this pull request
Feb 10, 2022
# [4.0.0-alpha.16](4.0.0-alpha.15...4.0.0-alpha.16) (2022-02-10) ### Bug Fixes * adding internal class (e.g. `_User`) fails due to prefixed underscore ([#2036](#2036)) ([f80bd07](f80bd07))
🎉 This change has been released in version 4.0.0-alpha.16 |
🎉 This change has been released in version 4.0.0-beta.4 |
mtrezza
pushed a commit
to mtrezza/parse-dashboard
that referenced
this pull request
Mar 23, 2022
mtrezza
pushed a commit
to mtrezza/parse-dashboard
that referenced
this pull request
Mar 23, 2022
* adding internal class (e.g. `_User`) fails due to prefixed underscore ([parse-community#2036](parse-community#2036)) ([f80bd07](parse-community@f80bd07))
mtrezza
pushed a commit
to mtrezza/parse-dashboard
that referenced
this pull request
Mar 23, 2022
* adding internal class (e.g. `_User`) fails due to prefixed underscore ([parse-community#2036](parse-community#2036)) ([f80bd07](parse-community@f80bd07)) * security upgrade prismjs from 1.26.0 to 1.27.0 ([parse-community#2047](parse-community#2047)) ([3afb24e](parse-community@3afb24e))
mtrezza
pushed a commit
to mtrezza/parse-dashboard
that referenced
this pull request
Mar 23, 2022
* adding internal class (e.g. `_User`) fails due to prefixed underscore ([parse-community#2036](parse-community#2036)) ([f80bd07](parse-community@f80bd07))
parseplatformorg
pushed a commit
that referenced
this pull request
Mar 23, 2022
# [4.1.0-alpha.1](4.0.1...4.1.0-alpha.1) (2022-03-23) ### Bug Fixes * adding internal class (e.g. `_User`) fails due to prefixed underscore ([#2036](#2036)) ([e004e70](e004e70)) * security upgrade prismjs from 1.26.0 to 1.27.0 ([#2047](#2047)) ([ffbca12](ffbca12)) * upgrade @babel/runtime from 7.17.0 to 7.17.2 ([#2055](#2055)) ([3e8449b](3e8449b)) * upgrade express from 4.17.2 to 4.17.3 ([#2058](#2058)) ([d1357de](d1357de)) * upgrade otpauth from 7.0.10 to 7.0.11 ([#2061](#2061)) ([05c5ac8](05c5ac8)) ### Features * change string filter description ([#2059](#2059)) ([6470c8e](6470c8e))
parseplatformorg
pushed a commit
that referenced
this pull request
Mar 23, 2022
# [4.1.0-beta.1](4.0.1...4.1.0-beta.1) (2022-03-23) ### Bug Fixes * adding internal class (e.g. `_User`) fails due to prefixed underscore ([#2036](#2036)) ([e004e70](e004e70)) * security upgrade prismjs from 1.26.0 to 1.27.0 ([#2047](#2047)) ([ffbca12](ffbca12)) * upgrade @babel/runtime from 7.17.0 to 7.17.2 ([#2055](#2055)) ([3e8449b](3e8449b)) * upgrade express from 4.17.2 to 4.17.3 ([#2058](#2058)) ([d1357de](d1357de)) * upgrade otpauth from 7.0.10 to 7.0.11 ([#2061](#2061)) ([05c5ac8](05c5ac8)) ### Features * change string filter description ([#2059](#2059)) ([6470c8e](6470c8e))
parseplatformorg
pushed a commit
that referenced
this pull request
Apr 3, 2022
# [4.1.0](4.0.1...4.1.0) (2022-04-03) ### Bug Fixes * adding internal class (e.g. `_User`) fails due to prefixed underscore ([#2036](#2036)) ([e004e70](e004e70)) * security upgrade prismjs from 1.26.0 to 1.27.0 ([#2047](#2047)) ([ffbca12](ffbca12)) * upgrade @babel/runtime from 7.17.0 to 7.17.2 ([#2055](#2055)) ([3e8449b](3e8449b)) * upgrade express from 4.17.2 to 4.17.3 ([#2058](#2058)) ([d1357de](d1357de)) * upgrade otpauth from 7.0.10 to 7.0.11 ([#2061](#2061)) ([05c5ac8](05c5ac8)) ### Features * change string filter description ([#2059](#2059)) ([6470c8e](6470c8e))
dblythy
pushed a commit
to dblythy/parse-dashboard
that referenced
this pull request
Apr 4, 2022
* adding internal class (e.g. `_User`) fails due to prefixed underscore ([parse-community#2036](parse-community#2036)) ([f80bd07](parse-community@f80bd07))
dblythy
pushed a commit
to dblythy/parse-dashboard
that referenced
this pull request
Jan 19, 2023
* adding internal class (e.g. `_User`) fails due to prefixed underscore ([parse-community#2036](parse-community#2036)) ([f80bd07](parse-community@f80bd07))
dblythy
pushed a commit
to dblythy/parse-dashboard
that referenced
this pull request
Jan 19, 2023
* adding internal class (e.g. `_User`) fails due to prefixed underscore ([parse-community#2036](parse-community#2036)) ([f80bd07](parse-community@f80bd07))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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
SpecialClasses from /lib/Constants.js already have the '_' prefix, so adding it will send a double underscore to the Parse server (e.g.: '__Installation' instead of '_installation'), which resolves in an Invalid classname error, based on the SchemaController's function 'validateNewClass'
Related issue: #2035
Approach
TODOs before merging