Google Git
Sign in
chromium/chromium/src/components/feedback/redaction_tool/refs/heads/main
commit
3977deb31296f86a6f79011aa7989349ea031383
[log]
author
Kalvin Lee <[email protected]>
Fri Feb 20 10:07:34 2026
committer
Copybara-Service <[email protected]>
Fri Feb 20 10:13:37 2026
tree
1239210821980b894da3557ac67431c5571575f1
parent
f72a6f34cb0ad624b7dea97966a2bb9eb147c1c7 [diff]
Spanify `RedactionTool` (2/2)

Convert `kBuiltInFirstPartyExtensionIds` to an array of
`std::string_view` and tweak functions as necessary.

Change the business logic to not expect a `nullptr` sentinel.

Fixed: 439455382
Change-Id: Ia79513fee6503c41b91726f2391f2d18c0a5267d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7544239
Reviewed-by: Xiangdong Kong <[email protected]>
Auto-Submit: Kalvin Lee <[email protected]>
Commit-Queue: Kalvin Lee <[email protected]>
Reviewed-by: Devlin Cronin <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1587695}
NOKEYCHECK=True
GitOrigin-RevId: edc4b56703ff9cb7bf14c95d72aa3b8efb98c305
3 files changed
tree: 1239210821980b894da3557ac67431c5571575f1
  1. test_data/
  2. BUILD.gn
  3. inprocess_metrics_recorder.cc
  4. inprocess_metrics_recorder.h
  5. inprocess_metrics_tester.cc
  6. inprocess_metrics_tester.h
  7. ip_address.cc
  8. ip_address.h
  9. metrics_tester.h
  10. pii_types.h
  11. README.md
  12. redaction_tool.cc
  13. redaction_tool.h
  14. redaction_tool_metrics_recorder.h
  15. redaction_tool_unittest.cc
  16. url_canon.h
  17. url_canon_internal.cc
  18. url_canon_internal.h
  19. url_canon_ip.cc
  20. url_canon_ip.h
  21. url_canon_stdstring.cc
  22. url_canon_stdstring.h
  23. url_parse.h
README.md

redaction_tool: PII Redaction Tool

A redaction_tool redacts the following PII using a wide set of RegEx expressions: kAndroidAppStoragePath kEmail kGaiaID kIPPAddress kIPAddress kLocationInfo kMACAddress kUIHierarchyWindowTitles kURL kSerial kSSID kStableIdentifier kVolumeLabel

The cros/upstream/main branch is a mirror of the components/feedback/redaction_tool directory from upstream.

How to update the source

To pull in updates from chromium/src, do the following:

  • git remote update

  • git checkout -b main cros/main

  • git merge cros/upstream/main

    • BUILD.gn should mostly use the version from main, unless the upstream changes the files to be built.
    • The #include paths should use the version from main (without “components/feedback”). This should be the majority of the merge conflicts.
    • In the commit message of the merge, list the commits from upstream that are merged.
    • If you need to do make changes to the merged commits (outside of conflicts), do that work in separate commits. For example, if you need to revert commits, use git revert after committing the merge commit. This preserves the history and makes it clear why a change is being reverted rather than quietly changing it in the merge commit.
    • Check the changes introduced by your merge by doing a diff against the commit before the merge. The difference should be the same as the changes in the upstream.

  • Push the resulting merge commit with:

    (chroot) $ git push HEAD:refs/for/main