How does the sorter work? about feathers-reactive HOT 7 CLOSED

What exactly are you trying to do? Creating your own sorter might be a bit complicated (the default one is being created from the query parameters using internals of the feathers-memory database adapter).

If you are just changing the query you might want to look at the solution from #39

from feathers-reactive.

I'm actually using that example just getting some strange behaviour.

This is the query I have set up

    this.query = new BehaviorSubject({
      $limit: 50,
      $skip: 0,
      published: true,
      $sort: {
        materialType: 1,
        weight: 1
      }
    });

then later on I have

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

this loads the data as expected, but if i then do a patch update on an item such as

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

the list is no longer sorted correctly, it seems to be sorted just by the weight attribute.

Oddly though, if I remove $limit and $skip from the query the sorting seems to stay correct.

from feathers-reactive.

$skip is definitely one of the edge cases where the normal smart strategy might not work because we won't know if the changed entry even still goes into that list.

If just the sorting is off there might still be a bug though. What database are you using?

from feathers-reactive.

I'm actually using the always strategy as I was finding the list would become empty when doing the same patch. I'm using mongo/mongoose for the database.

from feathers-reactive.

If the list becomes empty you may not have set the correct idField property.

from feathers-reactive.

Already have that set like

configure(rx(RxJS, {listStrategy: 'always', idField: '_id'}))

from feathers-reactive.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Apologies if the issue could not be resolved. FeathersJS ecosystem modules are community maintained so there may be a chance that there isn't anybody available to address the issue at the moment. For other ways to get help see here.

from feathers-reactive.