| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
return std::visit(There is also the absl::Overload alternative that is bit less cryptic, but we don't really have specific guidance for choosing one over the other
```
bool HasGuid(const Suggestion::Payload& payload) {
return std::visit(absl::Overload{
// Duplicated logic for these two types
[](const Suggestion::AutofillProfilePayload& p) { return !p.guid.value().empty(); },
[](const Suggestion::AutofillAiPayload& p) { return !p.guid.value().empty(); },
[](const Suggestion::Guid& p) { return !p.value().empty(); },
[](const auto&) { return false; } // Catch-all
}, payload);
}
```up to you
(base::FeatureList::IsEnabled(
autofill::features::kAutofillAiServerModel) &&
suggestion.type == SuggestionType::kFillAutofillAi)) {note that is usually be to but the feature flag at the very end in a chain of conditions, but in this case I think it doesn't really matter,
the idea being to only trigger (enroll the client into the an experimental group) when the feature is usable
but kFillAutofillAi is probably triggered way before this
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |