Re: [w3c/IndexedDB] boolean should be a valid key (#76)

Incidentally, what about `undefined` or `null` for that matter too (as for index keypaths set to test for the presence of `null` or (explicit or even sparse) `undefined`)?

And slightly off topic but interconnected, what exactly is the reason for the `IdentifierName` restrictions (such as no whitespace) comprising key paths (and the lack of a mode to escape full stops to allow for targeting any path)? Is there some crucial low-level reason for this, or was the decision made just to avoid foot-guns with inadvertently untrimmed paths?

It seems to me a pity that each point in a cloneable (or at least JSON) object can't, as it appears to me, be targeted for querying.

-- 
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/76#issuecomment-296501281