Report rest client errors, dispose coroutine scopes & disable last Next button #23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Catch&report errors raised by the REST client
the exceptions from the rest client were handled by
the coroutine scope which canceled everything in the
scope without any event logged to the user.
the exceptions are now catched inside the coroutine scope
& logged.
any error logged through the diagnostic logger is also displayed
in the Gateway UI through the internal errors message panel (red
balloon in the bottom right corner)
Dispose the coroutine scope when is no longer needed
disable next action button in the last step of the wizard when no IDE could be resolved