You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/api/enhancer.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ along side applyMiddleware.
53
53
-`config.profileParamsToPopulate`**([Array](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array)\|[String](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String))** Parameters within
54
54
profile object to populate. As of `v2.0.0` data is only loaded for population, not actually automatically populated
55
55
(allows access to both unpopulated and populated profile data).
56
-
-`config.autoPopulateProfile`**[Boolean](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Boolean)****NOTE**: Not yet enabled for v2.0.0. Whether or not to
56
+
-`config.autoPopulateProfile`**[Boolean](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Boolean)****NOTE**: Now enabled for v2.0.0. Whether or not to
57
57
automatically populate profile with data loaded through profileParamsToPopulate config. (default: `true`)
58
58
-`config.setProfilePopulateResults`**[Boolean](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Boolean)** Whether or not to
59
59
call SET actions for data that results from populating profile to redux under
Copy file name to clipboardExpand all lines: docs/queries.md
+47-48Lines changed: 47 additions & 48 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,6 +151,25 @@ firebaseConnect([
151
151
152
152
## Query Params
153
153
154
+
**Note:**`orderByChild`, `orderByValue`, and `orderByPriority` enable automatic parsing of query params that follow them for convince. This means that the order of query params can affect which query is created. For example:
155
+
156
+
```js
157
+
// Works since limitToFirst and startAt are parsed into numbers
@@ -314,18 +333,18 @@ The following are internally parsed:
314
333
*`boolean`
315
334
*`number`
316
335
317
-
This means the actual value will be parsed instead of the string containing the value. If you do not want this to happen, look at the `notParsed` query parameter below.
336
+
This means the actual value will be parsed instead of the string containing the value. If you do not want this to happen, look at the [`notParsed` query parameter below](#notParsed).
Can be used to keep internal parsing from happening. Useful when attempting to search a number string using `equalTo`
331
350
@@ -363,23 +382,3 @@ compose(
363
382
}))
364
383
)
365
384
```
366
-
367
-
## storeAs {#storeAs}
368
-
369
-
By default the results of queries are stored in redux under the path of the query. If you would like to change where the query results are stored in redux, use `storeAs`:
370
-
371
-
#### Examples
372
-
1. Querying the same path with different query parameters
0 commit comments