Incorrect sorting behavior, first record always positioned at the end v8.0.2. #4071
Comments
|
I found a few problems with this issue:
|
|
Saw similar behavior going from 8.0.1 to 8.0.2, in addition to problems propagating updates in my angular app... Downgrading to 8.0.1 fixes the problem... |
I am working with ionic 5 + angular. I also had a propagation problem in version 8.0.2, my solution was to go back to 8.0.0. |
|
I believe the issue is from angularfire, filed a issue there: angular/angularfire#2657 |
|
If it is AngularFire it's not 2657. As developers are reporting that they started encountering it with 8.0.2 IMO it's probably the JS SDK. |
|
@jamesdaniels Thanks! @heliomarpm I tried reproduce with angularfire and could not reproduce. Can you kindly provide a mini repro? This would greatly help me identifying the root cause quicker. |
|
This looks like #4079 @jamesdaniels Does AngularFire use |
|
@schmidt-sebastian I suspect you're right, AngularFire and RxFire use both old/newIndex: AngularFire |
Hello, after upgrading from v7.24.0 to v8.0.2, all the compositions are showing incorrect behavior, the first record is always being returned in the last position.
this.fireStore.doc(Users/${this.userId}) .collection<Card>('Cards', ref => ref.where('active', '==', true) .orderBy('order') .orderBy('createdAt', 'desc'));Example:
{order: 1, condition2: 'AA' ...}
{order: 2, condition2: 'BB' ...}
{order: 3, condition2: 'AB' ...}
{order: 4, condition2: 'DD' ...}
{order: 3, condition2: 'AB' ...}
Return:
{order: 2, condition2: 'BB' ...}
{order: 3, condition2: 'AB' ...}
{order: 3, condition2: 'AB' ...}
{order: 4, condition2: 'DD' ...}
{order: 1, condition2: 'AA' ...}
The text was updated successfully, but these errors were encountered: