W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: [IndexedDB] Key paths need to be specified better

From: Kyle Huey <me@kylehuey.com>
Date: Sat, 9 Jun 2012 16:27:52 -0700
Message-ID: <CAP045ArttFydbBcY5uYNX1VKZzYiMZg0xxNwRPYooz06q4NDAw@mail.gmail.com>
To: Odin Hørthe Omdal <odinho@opera.com>
Cc: public-webapps@w3.org
On Fri, Jun 8, 2012 at 10:42 AM, Odin Hørthe Omdal <odinho@opera.com> wrote:

> Kyle Huey <me@kylehuey.com> skreiv Fri, 08 Jun 2012 19:22:54 +0200
>  In particular the spec states that key paths are DOMStrings, and then
>> goes on to state how Array key paths are handled.  Whatever changes are
>> made need to preserve the note about key paths not nesting just after 4.7.1.
> Definately seconded. We've had some misunderstandings because of this. You
> can give an array of keyPaths both consumers, but IDBObjectStoreParameters
> is totally lying straight to our face by saying "DOMString?".
> IDBObjectStore.createIndex IDL is "any keyPath", which is correct. It may
> even be clearer to write (DOMString? keyPath or DOMString[] keyPath) or do
> an overload. You'd have to ask someone who knows WebIDL better :-)

I believe the correct type is "(DOMString or DOMString[])?".  That is, a
nullable union of DOMString or an array of DOMStrings.

- Kyle
Received on Saturday, 9 June 2012 23:28:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:34 UTC