commit | 228be95c585e9da1299c2c1144fd99baed1fc8ec | [log] [tgz] |
---|---|---|
author | Andrew Williams <awillia@chromium.org> | Thu Jan 26 15:13:01 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 26 15:13:01 2023 |
tree | a0e84fae7962a3a7cb01df7b6f85d9c38c22aaa9 | |
parent | f003a1d132348d1f78fec7dfbb63637e64cd15cc [diff] |
Rename UnguessableToken Deserialize2 to Deserialize This CL is part of a series to update base::UnguessableToken::Deserialize to return an absl::optional instead of an "empty" token in the case where deserialization fails. Previous CLs: 0. Add UnguessableToken::Deserialize method that returns optional - https://chromium-review.googlesource.com/c/chromium/src/+/4133328 1. Replace UnguessableToken::Deserialize with CreateForTesting in tests - https://chromium-review.googlesource.com/c/chromium/src/+/4162456 2. Use new UnguessableToken::Deserialize method in most places - https://chromium-review.googlesource.com/c/chromium/src/+/4135540 3. Return absl::optional from FromJavaUnguessableToken - https://chromium-review.googlesource.com/c/chromium/src/+/4135783 4. Return absl::optional from UnmarshalUnguessableToken - https://chromium-review.googlesource.com/c/chromium/src/+/4133481 5. Use new UnguessableToken::Deserialize in CreateForTesting - https://chromium-review.googlesource.com/c/chromium/src/+/4143338 6. Remove the old UnguessableToken::Deserialize - https://chromium-review.googlesource.com/c/chromium/src/+/4143958 Bug: 1402549 Change-Id: I2fda3d36e48e6af9b1e90d5a4fa2b1003546057a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4193090 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Owners-Override: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Andrew Williams <awillia@chromium.org> Cr-Commit-Position: refs/heads/main@{#1097381}
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.