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

Seems plausible.

I'm don't like the ever-growing list of methods as we add query types one by one and thus need to make them feature detectable, but we haven't come up with a good pattern for feature detecting options. (Or maybe we have and I just don't know?) Crazy thoughts like `query(range, {options})` and then a helper like `queryOptions({options})` that returns the options dict back to you as it was parsed (so unsupported options would vanish). But we should solve that for the whole platform, not just this spec/feature.

Is this a hint that Edge might be implementing here? :)


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