previous data lost when patch/remove with listStrategy='smart' about feathers-reactive HOT 7 CLOSED

It's probably because of idField not configure properly (which is set to id by default).

app.configure(reactive(RxJS, {listStrategy: 'smart', idField: '_id' }))

Should do it. I'll probably change and make it mandatory.

from feathers-reactive.

yes, now it works with idField configured.

from feathers-reactive.

I'll reopen this as a reminder to make idField mandatory.

from feathers-reactive.

I just hit this problem (the result list became empty after removing an item), and setting idField fixed it.

I don't suppose feathers-client can get the information about the id field from the server somehow, where it's already been configured?

from feathers-reactive.

Not really without adding service introspection which is not trivial to secure properly. I'm still making the change to have the id field being mandatory and potentially throwing an error if an item does not have the id field.

from feathers-reactive.

I'm experiencing a similar issue but only if I alter the original query.

For example I have a list of items with a published / unpublished status so on first load it shows all published items. If at this point if I mark an item as unpublished the list correctly updates. However if I update the list to say display unpublished items then try to update an item to published I get the behaviour described above where the data is lost.

This is my initial subscription, where the query is a BehaviourSubject

  getItems() {
    this.serviceSub = this.query.mergeMap(query => this.mainService.find({ query: query }));
    this.serviceSub.subscribe(resp => {
      this.total = resp.total;
      this.items = resp.data;
      this.isLoading = false;
    });
  }

This itself works fine in terms of updating the results but any patch updates afterwards fail.

This is what my patch request looks like

  unpublish(id:string, status: boolean) {
    this.mainService.patch(id, {published: status});
  }

from feathers-reactive.

Setting idField is now mandatory in v0.5.0 thanks to #58

from feathers-reactive.