-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Add ability to create classes without creating an object. #267
Add ability to create classes without creating an object. #267
Conversation
the race loser return before the race winner. This test failed in mongo 2.6.11, and I don't know if thats because it's generally flaky or if that version of mongo makes less guarantees.
@drew-gross updated the pull request. |
className === '_SCHEMA' || //TODO: remove this, as _SCHEMA is not a valid class name for storing Parse Objects. | ||
className === '_Role' || | ||
joinClassRegex.test(className) || | ||
classAndFieldRegex.test(className) |
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.
why not use fieldNameIsValid()
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.
This is to support legacy callers. The legacy callers should be updated, but that will have to come in a later PR.
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.
Oops, I misunderstood your original comment, GitHub was highlighting line 76 so I thought you were just talking about that line. Replacing this with fieldNameIsValid
is actually a good idea, I will do that and the other change and then merge this. Thanks for the review!
@drew-gross reviewed what I could. |
This will encode all ParseObject on the correct way so they can be translated into PFObject by the IOS SDK.
Thought it would be helpful to expose the example. It feels hidden in the docs right now.
If there is a default master key, people will inevitably use it. And that would be bad.
@drew-gross updated the pull request. |
Hmmm this PR now includes a bunch of random commits somehow. I'm going to close this and make a new one. |
This will be useful for schemas API POST.