[settings] Refactor VersionController
This CL shuffles around some code to prepare the VersionController to
track one version setting per storage type. The changes are:
* Change static accessors into readonly properties
* Move resetting the setting into a dedicated method
* Stash the setting as a private field
* Initialize the version setting directly with the current version
if the setting does not exist yet. This is functionally the same
as initializing it with zero and then immediatly resetting it
to current.
R=jarin@chromium.org
Bug: 1426748
Change-Id: I7d7ea759978b898717aa62d4f64f616af840eb14
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4359793
Commit-Queue: Simon Zünd <szuend@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Check out the project documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
DevTools frontend repository is mirrored on GitHub.
DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.
The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools