Skip to content

Explicitly define how to handle queryOrOptions being omitted in getAll/getAllKeys #475

@jfdoming

Description

@jfdoming

The IDL definition for getAll and getAllKeys lists queryOrOptions as optional; however, the algorithm 5.12 Creating a request to retrieve multiple items doesn't handle the case where queryOrOptions is not defined (and the description of the method doesn't either). There is the following note at the bottom of the algorithm:

NOTE: The range can be a key or key range (an IDBKeyRange) identifying the record items to be retrieved. If null or not given, an unbounded key range is used. If count is specified and there are more than count records in range, only the first count will be retrieved.

Based on the IDL as well as MDN and these Web Platform Tests, I think the note is meant to apply to queryOrOptions (it is not clear to me what range refers to here). Is that accurate? And if so, would it be worth updating the 5.12 algorithm to explicitly handle this case as a step?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions