applyChangesetFilterSortTarget doesn't work for sorted data when update/add records

[chuckn0rris]

Forum post

Open basic demo
In console

scheduler.store.applyChangeset({updated: [{id: 'r1', name : 'Adam2'}], added: [{id: 'r14', name : 'AAdam4'}] })

See sort has not been re-applied

[emilschutte]

This flag does not cause sorting in the general case. The config may need to be renamed. @bmblb what would you think about removing "sort" from this config name, since sorting is only selectively applied as needed to get any filtered-in records to appear in the right place?

[bmblb]

@emilschutte Renaming public config is problematic. We'd need to deprecate it first and then remove in the major release which would take significant time. Probably we could clarify documentation instead of renaming, explaining behavior in more details?

[emilschutte]

@bmblb 👍 sounds good to me.