Re: [w3c/IndexedDB] Add descending order for getAll() and getAllKeys() (#130)

SteveBeckerMSFT left a comment (w3c/IndexedDB#130)

This behavior is currently in Chrome/Edge Beta 142.  That is, updating `getAll()/getAllKeys()` to accept the `IDBGetAllOptions` dictionary, which adds direction support.  @phaux, have you experienced any issues?

Another alternative would add a third optional parameter for direction to `getAll()/getAllKeys()` while still using `getAllRecords()` as feature detection.  Adding this third optional parameter has no compat risk.  

However, using `IDBGetAllOptions` for `getAll()/getAllKeys()/getAllRecords()` both modernizes the APIs and provides consistency between APIs that perhaps we can build on with future enhancements.  For example, maybe we can add [request batching](https://github.com/w3c/IndexedDB/issues/376) using an array of `IDBGetAllOptions` dictionaries?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/130#issuecomment-3320296222
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/IndexedDB/issues/130/3320296222@github.com>