You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Improves further on Blazor reconnection experience.
- Expanded `ReconnectDisplay` to have a `rejected` method on it. This is the method that indicates we will never be able to reconnect to the server. By default we provide a nice little message letting users know that reconnection is no longer possible and that a refresh must take place.
- Added a logger to the `DefaultReconnectionDisplay` since part of its job is handling `Retry` clicks which indirectly call `reconnect()`. Therefore, it needed the ability to log information to the console to inform users why certain reconnects were not possible.
- Updated the `UserSpecifiedDisplay` to have a `refused` understanding. Added a new CSS class to represent the `refused` state as well.
- Updated existing tests to abide by the new `ReconnectDisplay` structure
- Added a new test to validate that the `refused``ReconnectDisplay` method results in proper behavior.
#12442
logger.log(LogLevel.Information,'Reconnection attempt failed. Unable to connect to the server.');
42
-
returnfalse;
43
-
}
44
-
45
40
if(!(awaitcircuit.reconnect(reconnection))){
46
-
logger.log(LogLevel.Information,'Reconnection attempt to the circuit failed.');
41
+
logger.log(LogLevel.Information,'Reconnection attempt to the circuit was rejected by the server. This may indicate that the associated state is no longer available on the server.');
0 commit comments