commit | 2eb6d2468290b4bd6ea4926bd4bd265418ce3522 | [log] [tgz] |
---|---|---|
author | Alison Gale <agale@chromium.org> | Fri Apr 05 18:41:13 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 05 18:41:13 2024 |
tree | 23904d8f100a4218a6b95d90850ad58231f73896 | |
parent | 5a03e086b849098bff3dc71d2092629e21e4fc89 [diff] |
Move all pref handling to static prompt manager functions Not adding any logic here, just a final move of these classes based on needs dictated by diagramming out all cases we need to consider. Also for naming I had gotten feedback recently about not needing to be redundant between the class name and method name in some cases so I went a bit shorter for some of the names but I'm happy to expand them if that clarity is needed. Also sorted the methods to group static and non-static methods together. The style guide is not very specific so I tried to take parts from that and parts from other classes we use frequently. Open to other ordering if it makes more sense. Diagram of cases to consider: https://screenshot.googleplex.com/BH6A7Wtz9M5h58y Bug: 330780464 Change-Id: I198186121eca30ff543c40408f899fce9a0121e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5429023 Reviewed-by: Eshwar Stalin <estalin@chromium.org> Commit-Queue: Alison Gale <agale@chromium.org> Reviewed-by: Charles Meng <charlesmeng@chromium.org> Cr-Commit-Position: refs/heads/main@{#1283288}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.