Skip to content

Commit d3b2bc2

Browse files
committed
Added section on querying and pagination
1 parent fe12abf commit d3b2bc2

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

README.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -362,9 +362,13 @@ It's possible that you'll want to store pagination information for more than one
362362
}
363363
```
364364

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+
365369
### The `find` getter
366370

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:
368372

369373
**`params = { query: {} }`**
370374
```js

0 commit comments

Comments
 (0)