| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
filter_ ? filter_->LastEffect() : nullptr, kInterpolationSpaceSRGB);Maybe add a `LastEffect()` accessor to reduce the noise a bit here?
if (filter_data_) {Could this be merged with one of the existing blocks? (The one below seems like the prime candidate.)
FilterOperation* op = filter.Operations()[0].Get();
To<ReferenceFilterOperation>(*op).SetFilter(filter_data_->GetFilter());Why not just:
```suggestion
To<ReferenceFilterOperation>(*filter.at(0)).SetFilter(filter_data_->GetFilter());
```
to keep accesses consistent with the above ones (and shorter)?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Auto-Submit | +1 |
| Commit-Queue | +1 |
filter_ ? filter_->LastEffect() : nullptr, kInterpolationSpaceSRGB);Maybe add a `LastEffect()` accessor to reduce the noise a bit here?
Done
Could this be merged with one of the existing blocks? (The one below seems like the prime candidate.)
Done
FilterOperation* op = filter.Operations()[0].Get();
To<ReferenceFilterOperation>(*op).SetFilter(filter_data_->GetFilter());Why not just:
```suggestion
To<ReferenceFilterOperation>(*filter.at(0)).SetFilter(filter_data_->GetFilter());
```
to keep accesses consistent with the above ones (and shorter)?
This is due to filter.at returning a const filter operation. Using `filter.Operations()` is following the same pattern as is used by `BuildFilterOperations`.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |