-
Notifications
You must be signed in to change notification settings - Fork 21
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: unify ucan api endpoints #328
Conversation
packages/api-gateway/src/index.js
Outdated
? await toBuffer(toIt(request.body)) | ||
: Uint8Array.from([]), | ||
}) | ||
if (invocations.length !== 1) { |
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.
We should requests to carry a single invocations, it's been designed to send batches of invocations in a single request.
Also I think you don't need to do most of these, you could simply define a server just like you usually would except don't wrap handler in provider
that way handler will be called without performing any kind of validation and you'll be able to execute it on desired connection.
51fe560
to
83ff9b6
Compare
lots of ugly commits for what was ultimately a silly mistake in my github workflow yaml. My bad. We'll squash when this PR merges. Good news is now commits to api-gateway will get a dev deployment, e.g. https://refs-heads-325-unify-ucan-api-endpoints.protocol-labs.workers.dev/ tomorrow I will test it using access-client and upload-client |
c26978e
to
4cfe312
Compare
Status
|
Motivation:
Status
Parts