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: README.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -362,9 +362,13 @@ It's possible that you'll want to store pagination information for more than one
362
362
}
363
363
```
364
364
365
+
> Note: The `find` action no longer returns reactive lists. The list data will still be reactive, but new matches that arrive from the server do NOT get automatically added to lists. There are two solutions to this:
366
+
- Use the `find` action to pull in data from the server. Use the `find` getter to pull a reactive list from the store.
367
+
- Configure the `feathers-reactive` plugin with RxJS on your Feathers Client instance. [Read the docs for implementation details.](https://github.com/feathersjs/feathers-reactive)
368
+
365
369
### The `find` getter
366
370
367
-
The `find` getter queries data from the local store using the same Feathers query syntax as on the server. It is synchronous and directly returns the results of the query. Pagination is **always** enabled and cannot be disabled. It accepts a params object with a `query` attribute. It does not use any other special attributes. The returned object looks just like a paginated result that you would receive from the server:
371
+
The `find` getter queries data from the local store using the same Feathers query syntax as on the server. It is synchronous and returns the results of the query with pagination. Pagination cannot be disabled. It accepts a params object with a `query` attribute. It does not use any other special attributes. The returned object looks just like a paginated result that you would receive from the server:
0 commit comments