[w3c/IndexedDB] Add getAllRecords() method and update getAll()/getAllKeys to support direction option (PR #461)

Closes #206 #130 

The following tasks have been completed:

 * [X] Confirmed there are no ReSpec/BikeShed errors or warnings.
 * [X] Modified Web platform tests (link to pull request)

### WPT coverage:
getAllRecords():
//IndexedDB/idbobjectstore_getAllRecords.tentative.any.js
//IndexedDB/idbindex_getAllRecords.tentative.any.js

getAll()/getAllKey() direction option: 
//IndexedDB/idbobjectstore_getAllKeys-options.tentative.any.js
//IndexedDB/idbindex_getAllKeys-options.tentative.any.js
//IndexedDB/idbobjectstore_getAll-options.tentative.any.js
//IndexedDB/idbindex_getAll-options.tentative.any.js

Implementation commitment:

 * [ ] WebKit (https://bugs.webkit.org/show_bug.cgi?id=)
 * [X] Chromium (https://issues.chromium.org/issues/40746016)
 * [ ] Gecko (https://bugzilla.mozilla.org/show_bug.cgi?id=)

### Outline of change:

#### Potentially valid key range

Added to support overloading getAll()/getAllKeys() with IDBGetAllOptions as the first argument.   Preserves existing behavior for key ranges and keys.  Avoids parsing the first argument for getAll()/getAllKeys() as a IDBGetAllOptions when the argument is a key range or has a type that could be a valid key (Number, String, Date, ArrayBuffer, or Array).

#### Record snapshot

Added for the output of getAllRecords(), which includes the record's key, value and primaryKey.  For IDBIndex, key is the index key and primaryKey is the record's key.  Required because object stores and indexes define different types of records.

#### getAll()/getAllKeys()

Methods updated to support overload of the first argument, which is either a key range or an IDBGetAllOptions.  IDBGetAllOptions adds direction support.

#### getAllRecords()

New method added to both IDBObjectStore and IDBIndex.  Supports IDBGetAllOptions only.

#### Retrieve multiple items from an object store/index

Algorithm updated to include more inputs: kind and direction.  Kind determines the type of output, which is either keys, values or record snaptshots.  Direction determines the sorting of the output, which is either ascending or descending.


<!--
    This comment and the below content is programmatically generated.
    You may add a comma-separated list of anchors you'd like a
    direct link to below (e.g. #idl-serializers, #idl-sequence):

    Don't remove this comment or modify anything below this line.
    If you don't want a preview generated for this pull request,
    just replace the whole of this comment's content by "no preview"
    and remove what's below.
-->
***
<a href="https://pr-preview.s3.amazonaws.com/w3c/IndexedDB/pull/461.html" title="Last updated on Jun 24, 2025, 11:50 PM UTC (c5462df)">Preview</a> | <a href="https://pr-preview.s3.amazonaws.com/w3c/IndexedDB/461/95f98c0...c5462df.html" title="Last updated on Jun 24, 2025, 11:50 PM UTC (c5462df)">Diff</a>
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/IndexedDB/pull/461

-- Commit Summary --

  * Initial commit

-- File Changes --

    M index.bs (515)

-- Patch Links --

https://github.com/w3c/IndexedDB/pull/461.patch
https://github.com/w3c/IndexedDB/pull/461.diff

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/pull/461
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/IndexedDB/pull/461@github.com>