Watch behavior is confusing

[v3g42]

https://github.com/getdozer/dozer-react#usedozerendpointqueryendpoint-string-options--query-dozerquery-watch-eventtype-

Problem

Currently watch maintains a limit of certain size when additional records are fetched from the server. And what remains and what doesn't remain is completely ad-hoc.

Solution

• [ ] Add optional field called trim or maxSize. Users need to specifically mention that records have to be trimmed. Default behavior is that we don't trim.

• [ ] Default behavior is that list keeps growing. DOnt implement any pagination controls. If users want pagination, they should implement one themselves or use a grid library provided in the samples.

• [ ] Host a story book with a few samples available and all the parameters.

Problem

• [ ] If watch is only using OnEvent method, responses are very misleading. This is not expected behavior and also not usable for any real world use case.

Solution

Either

• [ ] break down query + watch into separate methods

(or)

• [ ] Implement a method to start Streaming + query using pagination based on conditions. THis is quite complex to implement and should be sparingly used.

[chubei]

I like a maxSize parameter and FIFO eviction policy. I imagine that's what a developer wants out of the box. We can implement this using query + on_event.

Pagination is too complex to fit in the library can be left in a sample.