App now initializes the connection instead of term control. #1676
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.
Summary of the Pull Request
We want TermControl to be agnostic to the type of connection, so the connection initialization has been moved to TerminalApp.
References
PR Checklist
Detailed Description of the Pull Request / Additional comments
The TermControl constructor has been modified to take in a connection, thus TermControl does not need to initialize a connection anymore. Instead, TerminalApp initializes the connection and passes it into the TermControl constructor. Thus once we start allowing different types of connections (an Azure connection for example), the detection of the type of connection only needs to happen in TerminalApp.
Validation Steps Performed