commit | 35bd1af66a607f6c3a9ccee9ad5772020d102641 | [log] [tgz] |
---|---|---|
author | Jennifer Serrano <jennserrano@google.com> | Thu Nov 07 00:40:01 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 07 00:40:01 2024 |
tree | 17fb51e87793cb6b9a9d68ebc6a0ee8bf4d52c90 | |
parent | 70b06606b3baef3d1db1b5629807877932f9a59d [diff] |
[ntp][enterprise] Move calendar fake data creation to separate file Google and Outlook calendar use the same mojom structs so fake data creation for the most part remains the same. Bug: 357102078 Change-Id: Ic014bb67a48eeba33e72d7c7b3616467c306c1e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6001093 Commit-Queue: Jennifer Serrano <jennserrano@google.com> Reviewed-by: Riley Tatum <rtatum@google.com> Cr-Commit-Position: refs/heads/main@{#1379382}
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.