Skip to content

Add ChannelValue type for result and stdio channels#27

Open
martin-henz wants to merge 3 commits into
mainfrom
channel-types
Open

Add ChannelValue type for result and stdio channels#27
martin-henz wants to merge 3 commits into
mainfrom
channel-types

Conversation

@martin-henz
Copy link
Copy Markdown
Member

As per discussion in "SA 2627 Conductor" telegram channel, this PR gets rid of "any" type in channel messages using a new ChannelValue type and provides a mandatory string field that lets the frontend display the value in a REPL.

This PR was created with the help of Claude Code (Opus 4.6).

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request transitions the communication channels for standard I/O and results from simple strings and any types to a structured ChannelValue interface, which includes a mandatory string representation and an optional rich payload. These changes affect the host and runner plugins as well as their respective interfaces. A minor suggestion was made to maintain alphabetical order in the type exports.

export type { IErrorMessage } from "./IErrorMessage";
export type { IIOMessage } from "./IIOMessage";
export type { IResultMessage } from "./IResultMessage";
export type { ResultPayload } from "./ResultPayload";
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The export for ResultPayload is currently out of alphabetical order. To maintain consistency and improve readability, it should be moved after IStatusMessage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant