Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Currently a call to Ignition.startClient return client instance even if we know for sure that connection is not usable. Real exception (e.g. protocol mismatch, auth error, etc.) is thrown on attempt to execute first operation on the client. This is bad UX - use may think that everything is OK for a long time.
Instead, connection should be established eagerly in startClient, any exception should be propagated to the user immediately.
Attachments
Issue Links
- links to