| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
LGTM, this looks reasonable, thanks for doing this! 😄
One good thing here is that we can now also use the `matches` logic to clump multiple filters together and have `WebAppFilter` be some sort of a builder pattern, so that we can use multiple WebAppFilters while trying to fetch a single app. Nice!
if (const auto& iwa_filter = filter.isolated_app_filter_) {Interesting, I wonder how this works? Isn't `iwa_filter` a `std::optional<>`? In that case, won't this conditional always be true? Or does it reference to a value under the hood, and returns a nullptr if it's `std::nullopt`?
{proto::InstallState::SUGGESTED_FROM_ANOTHER_DEVICE,This is a subtle behavior change, as apps coming in via sync (`SUGGESTED_FROM_ANOTHER_DEVICE`) will no longer be considered as valid for this function. I think it's fine, because IWAs aren't synced (afaik!), right?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
raw_ptr<IwaPermissionsPolicyCache> cache_;Hidden change here, of the `cache_` being removed :p, and instead obtaining the permissions policy factory from the profile!
Totally fine for the time being since we're removing a raw_ptr (yay!), but if this CL breaks things and needs to be reverted, this logic will need to be re-added again.
if (const auto& iwa_filter = filter.isolated_app_filter_) {Interesting, I wonder how this works? Isn't `iwa_filter` a `std::optional<>`? In that case, won't this conditional always be true? Or does it reference to a value under the hood, and returns a nullptr if it's `std::nullopt`?
`if (<decl> var = func()) { ... }` is equal to
```
{
<decl> var = func();
if (var) {
...
}
}
```So it will behave like a normal optional!
{proto::InstallState::SUGGESTED_FROM_ANOTHER_DEVICE,This is a subtle behavior change, as apps coming in via sync (`SUGGESTED_FROM_ANOTHER_DEVICE`) will no longer be considered as valid for this function. I think it's fine, because IWAs aren't synced (afaik!), right?
They're not; this code looks like a remnant from some other age where people weren't sure about anything IWA-related!
| 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 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
TEST_F(I'm sometimes honestly shocked by how many ad-hoc tests we have that rely on some customly crafted conditions (incl. modifying the registrar directly) instead of actually testing the prod flows!
| 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 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |