Make the ParseObject construct throw more specific exceptions #56
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.
In a scenario of a developer not utilizing
ParseClient::initialize
before calling another object such asnew ParseUser()
, the user receives a message about specifying a Parse class name or usingParseObject::create
, throwing them in the wrong direction about their error. This commit adds one more line to the Exception asking them if they in fact remembered to useParseClient::initialize
before being thrown away from their obvious mistake - this should prevent questions like these or #55 from occurring.The resulting Exception now displays as such: