commit | d9175b2f2c62d964d6b15968e0a71bf1d0bae040 | [log] [tgz] |
---|---|---|
author | Christoph Schwering <schwering@google.com> | Fri Dec 06 16:40:54 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 06 16:40:54 2024 |
tree | 76bb818ead7046c22a94b45fca115ec0ccd7e953 | |
parent | 3568120a41e7b71f19be9ec58fe582cc14b80a6e [diff] |
[Autofill] Rename some functions, variables in VotesUploader This CL renames some variables and functions for more consistency in VotesUploader: - `OnSubmissionFieldTypesDetermined()` --> OnFieldTypesDetermined()` Reason: the meaning of "submission" is unclear, especially since the function is also called with `is_submission = false`. - `FlushPendingVotes()` --> FlushQueuedVotes()` Reason: avoid two concepts for the same thing; originally I had thought I'd need the term "pending" for asynchronous tasks. - `QueuedVote::callback` --> `QueuedVote::upload_vote` Reason: more descriptive. - `interaction_time` --> `initial_interaction_timestamp` `submittion_time` --> `submission_timestamp` Reason: consistency. - `source_id` --> `ukm_source_id` Reason: consistency. - `queued_vote_uploads_` --> `queued_votes_` Reason: consistency with the type name. - `form_structure` --> `form` Reason: reduce noise; there are no non-FormStructure forms in VotesUploader. Bug: 374086145 Change-Id: I05e4454055509f802cbbccd6cf382e887bad5cbb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6074473 Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Reviewed-by: Dominic Battré <battre@chromium.org> Commit-Queue: Christoph Schwering <schwering@google.com> Cr-Commit-Position: refs/heads/main@{#1392952}
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.