Design a way for TerminalConnections to receive arbitrary (JSON?) arguments #5627

Open
opened 2026-01-31 00:17:45 +00:00 by claunia · 1 comment
Owner

Originally created by @DHowett-MSFT on GitHub (Dec 17, 2019).

This will allow a connection type to peer into the profile that spawned it to get more information out of it, like a port from a telnet profile and a username from an SSH profile.

Originally created by @DHowett-MSFT on GitHub (Dec 17, 2019). This will allow a connection type to peer into the _profile_ that spawned it to get more information out of it, like a `port` from a telnet profile and a `username` from an SSH profile.
Author
Owner

@zadjii-msft commented on GitHub (Nov 22, 2021):

More or less, this was done with #10184. A ValueSet is basically a jsonblob. Whenever we eventually get around to allowing other connection types, that's how we'll do it.

@zadjii-msft commented on GitHub (Nov 22, 2021): More or less, this was done with #10184. A `ValueSet` is basically a jsonblob. Whenever we eventually get around to allowing other connection types, that's how we'll do it.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#5627