748ebddf0773a4c8902911c6080349aee6f2dea4
ImporterURLRow in a modularised component
`chrome/common/importer/importer_url_row.h` is now under `//components`. This change corrects the inclusion header, as well as the deps for the sources making use of this type. Chromium changes: https://chromium.googlesource.com/chromium/src/+/92d2bd6e1e191227c779fcee6f26cf6a7f77740a commit 92d2bd6e1e191227c779fcee6f26cf6a7f77740a Author: Alexis Hetu <sugoi@chromium.org> Date: Tue May 13 08:48:51 2025 -0700 Add //components/importer We are working on adding data import functionality to //ios/chrome. To facilitate reusing existing importation code, as well as possible sharing/reuse of the new code we will be adding, we would like to add a new components directory. The use case here is for platform-independent logic relating to data import, such as intermediary data structures, translation logic, and interactions with other components-layer model objects (such as bookmark storage). This shared code is needed in multiple places in Chrome that couldn't otherwise share code without this component: * //ios/chrome * //chrome/browser/importer * //chrome/common/importer * //chrome/utility/importer As an example of the intended structure/how this component will be used, I've moved one existing file from //chrome/common/importer into //components/importer/core. This is a data structure we intend to reuse verbatim, so it's a simple test case. As mentioned in the README, we will also create a //components/importer/safari subdirectory, but that code requires some nontrivial architecture discussions, so I elected not to add that subdirectory in this initial CL. See also design doc (sorry, Googlers only): go/bling-import Change-Id: Iedbc1314935a9d098fb5f84ab37df186b5af082a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6505547 Reviewed-by: Colin Blundell <blundell@chromium.org> Commit-Queue: Alexis Hétu <sugoi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1459474}
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
Brave Core
Brave Core is a set of changes, APIs, and scripts used for customizing Chromium to make the Brave browser. Please also check https://github.com/brave/brave-browser
Follow @brave on Twitter for important announcements.
Resources
Community
You can ask questions and interact with the community in the following locations:
- Brave Community
communitychannel on Brave Software's Slack
Languages
C++
36.9%
HTML
31.6%
Swift
9.4%
TypeScript
9%
Java
4.8%
Other
8.1%