-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat!: versioned transport protocol #274
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AgentMessage
is a good abstraction over the various ways ucanto can be configured to send messages (e.g. so apps using ucanto can transition from legacy
to ucan invocation spec )
@@ -417,3 +418,53 @@ test('falsy errors are turned into {}', async () => { | |||
ok: {}, | |||
}) | |||
}) | |||
|
|||
test('run invocation without encode / decode', async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome!
Co-authored-by: Benjamin Goering <[email protected]>
Overview
AgentMessage
block which are DAGs send around between ucanto (client/server) agents.AgentMessage
may contain set of delegations (to be invoked) and / or set of receipts.AgentMessage
is represented as a variant case so we could introduce another version in the future (e.g. when ucan invocations are implemented)AgentMessage
-es and no longer know or care what they contain.