Insist on the difference between 'first' and 'get' (#590)

Olivier Allouch · flovilmart · commit acdb6452fc6a · 2018-06-29T15:53:51.000-04:00
Users shouldn't expect an undefined when calling get.
diff --git a/src/ParseQuery.js b/src/ParseQuery.js
@@ -382,7 +382,7 @@ class ParseQuery {
   /**
    * Constructs a Parse.Object whose id is already known by fetching data from
    * the server.  Either options.success or options.error is called when the
-   * find completes.
+   * find completes. Unlike the <code>first</code> method, it never returns undefined.
    *
    * @param {String} objectId The id of the object to be fetched.
    * @param {Object} options A Backbone-style options object.

Original file line number	Diff line number	Diff line change
`@@ -382,7 +382,7 @@ class ParseQuery {`
`382`	`382`	`/**`
`383`	`383`	`* Constructs a Parse.Object whose id is already known by fetching data from`
`384`	`384`	`* the server. Either options.success or options.error is called when the`
`385`		`- * find completes.`
	`385`	`+ * find completes. Unlike the <code>first</code> method, it never returns undefined.`
`386`	`386`	`*`
`387`	`387`	`* @param {String} objectId The id of the object to be fetched.`
`388`	`388`	`* @param {Object} options A Backbone-style options object.`