-
Notifications
You must be signed in to change notification settings - Fork 93
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
Typescript sdk standardization #700
Typescript sdk standardization #700
Conversation
Seems ok to me! |
Thank you both! While reviewing this I noticed that you’ve hard-coded the Datastar version number in datastar/sdk/typescript/src/node/node.ts Line 13 in a4c2e87
datastar/sdk/typescript/src/web/deno.ts Line 10 in a4c2e87
|
Right, good point |
@nickchomey I've done some changes to the comments, does that make keepalive more clear to you ? |
Thanks, those comments are helpful re: Though, perhaps before merging this, let me dig into the sdk today and report back later with any further feedback |
Ive done a bit of testing and it seems fine. I'll be sure to report any issues or improvements if I find them |
@Superpat please resolve the conflicts and report the current status. |
But still allow passing of stricter types when it makes sense
we want the stream to be ended only if keepalive is not present
The stream is closed automatically after the callback runs. The only situation where we want to use keepalive is if we want an infinite stream, in which case we dont want to close it.
this sdk is also used in javascript where there's less type information
8be3710
to
8ed5bd5
Compare
@bencroker done |
Merged, thank you both! |
Fixes a bug in my last pr that was pointed out by @nickchomey and closes #603
I decided to keep both api's since it was pretty simple.
Maybe wait till @nickchomey has reviewed this since he found out the flaw in the last pr.