Re: [w3c/IndexedDB] Adjust how the direction is defaulted in "Creating a request to retrieve multiple items" (PR #478)

SteveBeckerMSFT left a comment (w3c/IndexedDB#478)

Thanks for identifying this issue and proposing a fix.  #475 also reported this issue.  Maybe we should update "[creating a request to retrieve multiple items](https://w3c.github.io/IndexedDB/#create-a-request-to-retrieve-multiple-items)" to explicitly handle an undefined `queryOrOptions`?

Prior to `getAllRecords()`, the steps for "[convert a value to a key range ](https://w3c.github.io/IndexedDB/#convert-a-value-to-a-key-range)" handled undefined values.  Specifically, step 2, which returns an unbounded key range for an undefined value.

> If value is undefined or is null, then [throw](https://webidl.spec.whatwg.org/#dfn-throw) a "[DataError](https://webidl.spec.whatwg.org/#dataerror)" [DOMException](https://webidl.spec.whatwg.org/#idl-DOMException) if null disallowed flag is true, or return an [unbounded key range](https://w3c.github.io/IndexedDB/#unbounded-key-range) otherwise.

We could update step 8 in "[creating a request to retrieve multiple items](https://w3c.github.io/IndexedDB/#create-a-request-to-retrieve-multiple-items)" to say something like this: 

> If queryOrOptions is undefined or running [is a potentially valid key range](https://w3c.github.io/IndexedDB/#is-a-potentially-valid-key-range) with queryOrOptions is true, then:

Thoughts?

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

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