commit | c4455006b375352460fa5de88c1a3392957498e3 | [log] [tgz] |
---|---|---|
author | David Maunder <davidjm@google.com> | Fri Jun 03 20:27:47 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 03 20:27:47 2022 |
tree | c553bd74c43d06fa99402d108d0d887f60cdba89 | |
parent | 0757c8bad4fbf0173ea9793a0e8f124b70133572 [diff] |
Move EndpointFetcher to //components As part of our efforts to build a cross-platform Shopping API we are moving the EndpointFetcher to //components. This has been achieved by making the EndpointFetcher depend explicitly on URLLoaderFactory, IdentityManager and is stable channel determination. In the future we will consider doing a //components/endpoint_fetcher/content specific implementation (which can depend on //content) and an iOS specific implementation to make the constructor simpler e.g. client only needs to pass in a BrowserContext/BrowserState rather than needing to pull a URLLoaderFactory off it and pass that in. The EndpointFetcher has clients outside of Shopping so the EndpointFetcher is being moved to //components and not //components/commerce. For more details on our efforts to move our modules to //components see go/shopping-infra-to-components. Bug: 1329520 Change-Id: Id3a61b6837b58e3032bfdc8edac42983d17259ad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3677281 Reviewed-by: Ted Choc <tedchoc@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Commit-Queue: David Maunder <davidjm@chromium.org> Reviewed-by: Matt Menke <mmenke@chromium.org> Reviewed-by: David Roger <droger@chromium.org> Reviewed-by: George Benz <gbj@google.com> Reviewed-by: Wei-Yin Chen <wychen@chromium.org> Cr-Commit-Position: refs/heads/main@{#1010729}
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.