RESOLVED FIXED 84208
[Chromium] IndexedDB: Prep for changing keyPath return type
https://bugs.webkit.org/show_bug.cgi?id=84208
Summary [Chromium] IndexedDB: Prep for changing keyPath return type
Joshua Bell
Reported 2012-04-17 16:31:28 PDT
[Chromium] IndexedDB: Prep for changing keyPath return type
Attachments
Patch (6.78 KB, patch)
2012-04-17 16:34 PDT, Joshua Bell
no flags
Patch (5.14 KB, patch)
2012-04-18 09:51 PDT, Joshua Bell
no flags
Joshua Bell
Comment 1 2012-04-17 16:34:34 PDT
WebKit Review Bot
Comment 2 2012-04-17 16:39:52 PDT
Please wait for approval from abarth@webkit.org, dglazkov@chromium.org, fishd@chromium.org, jamesr@chromium.org or tkent@chromium.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI.
Joshua Bell
Comment 3 2012-04-17 16:44:58 PDT
FYI, the Chromium side is at: https://chromiumcodereview.appspot.com/10041014 This will end up being a 5-part patch: (1) WebKit prep: keyPath -> keyPathString rename (2) Chromium prep: keyPath -> keyPathString rename (3) WebKit API change: WebIDBKeyPath type addition to the API, with compat shims (4) Chromium use of the new API (5) implementation in WebCore of the new IDB functionality (and drop shims)
David Grogan
Comment 4 2012-04-17 18:44:16 PDT
Comment on attachment 137631 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=137631&action=review LGTM > Source/WebKit/chromium/src/WebIDBIndexImpl.h:48 > + virtual WebString keyPathString() const OVERRIDE; You probably already know, but you can leave off the OVERRIDEs for WebKit API overrides if they make commit engineering difficult.
James Robinson
Comment 5 2012-04-17 18:46:55 PDT
Comment on attachment 137631 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=137631&action=review > Source/WebKit/chromium/public/WebIDBIndex.h:2 > + * Copyright (C) 2012 Google Inc. All rights reserved. we don't do this in WebKit. leave the date alone >> Source/WebKit/chromium/src/WebIDBIndexImpl.h:48 >> + virtual WebString keyPathString() const OVERRIDE; > > You probably already know, but you can leave off the OVERRIDEs for WebKit API overrides if they make commit engineering difficult. we typically don't use OVERRIDE for things in the WebKit API. The hard rule is that if the declaration you are overriding is in a different repository, do not use OVERRIDE cos it'll make staging changes difficult. In this case, keyPathString() is in the same repo so that shouldn't be an issue - but we also say to favor consistency, which would be a strike against using OVERRIDE here. So on balance I think you should not add OVERRIDE here unless you want to do it everywhere
Joshua Bell
Comment 6 2012-04-18 09:51:45 PDT
Joshua Bell
Comment 7 2012-04-18 09:52:42 PDT
Oops, thanks. So eager to be done I was dotting t's and crossing i's. :) Take another look?
Joshua Bell
Comment 8 2012-04-18 14:21:24 PDT
@abarth or @fishd - can you take a look?
Joshua Bell
Comment 9 2012-04-18 15:22:07 PDT
or dglazkov@ ?
Kent Tamura
Comment 10 2012-04-19 16:21:03 PDT
Comment on attachment 137714 [details] Patch ok
WebKit Review Bot
Comment 11 2012-04-19 17:58:28 PDT
Comment on attachment 137714 [details] Patch Clearing flags on attachment: 137714 Committed r114708: <http://trac.webkit.org/changeset/114708>
WebKit Review Bot
Comment 12 2012-04-19 17:58:33 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.