| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
// Dismiss the payments suggestions.```suggestion
// Dismisses the passkey creation bottom sheet.
```
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
// Coordinator in charge of the presenting the passkey creation bottom sheet.
@property(nonatomic, strong) PasskeyCreationBottomSheetCoordinator*
passkeyCreationBottomSheetCoordinator;Since we're trying to move away from properties, I think the recommendation for the BrowserCoordinator is to use ivars for new coordinators
if (self.passkeyCreationBottomSheetCoordinator) {
return;
}I think this is risky. If the coordinator is never stopped for whatever reason (e.g., race condition, poor implementation), this part of the UI will become blocked. I think we prefer overriding the previous instance with the new one in such cases
go/coordinator-fix-proposal
- (void)viewDidDisappear {
[self.browserCoordinatorCommandsHandler dismissPasskeyCreation];
}We are moving away from message forwarding go/bling-best-practices#message-forwarding
If the method isn't going to do more than call `dismissPasskeyCreation`, then the commands handler should be passed to and used by the view controller directly
// Returns the matcher for the use password button.```suggestion
// Returns the matcher for the "Create" button.
```
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
// Coordinator in charge of the presenting the passkey creation bottom sheet.
@property(nonatomic, strong) PasskeyCreationBottomSheetCoordinator*
passkeyCreationBottomSheetCoordinator;Since we're trying to move away from properties, I think the recommendation for the BrowserCoordinator is to use ivars for new coordinators
Done
if (self.passkeyCreationBottomSheetCoordinator) {
return;
}I think this is risky. If the coordinator is never stopped for whatever reason (e.g., race condition, poor implementation), this part of the UI will become blocked. I think we prefer overriding the previous instance with the new one in such cases
go/coordinator-fix-proposal
Ok. Removed.
- (void)viewDidDisappear {
[self.browserCoordinatorCommandsHandler dismissPasskeyCreation];
}We are moving away from message forwarding go/bling-best-practices#message-forwarding
If the method isn't going to do more than call `dismissPasskeyCreation`, then the commands handler should be passed to and used by the view controller directly
Done (also modified in the previous CL accordingly).
// Dismiss the payments suggestions.Alexis Hétu```suggestion
// Dismisses the passkey creation bottom sheet.
```
Done
```suggestion
// Returns the matcher for the "Create" button.
```
| 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. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |