-
Notifications
You must be signed in to change notification settings - Fork 55
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
Full coverage kv management methods #535
Full coverage kv management methods #535
Conversation
Ivandemidov00
commented
Jul 2, 2024
•
edited by mtmk
Loading
edited by mtmk
- resolves Ensure full coverage of KV management methods #510
@mtmk I couldn't find the CreateOrUpdateStream api. Do I correctly understand that it is impossible to implement the CreateOrUpdateStore method without calling the server twice? Is CreateOrUpdateStore necessary under such conditions? |
Well spotted. let's leave that out. afaik there is no create-or-update stream call. cc @Jarema |
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.
Aside from two minor suggestions, this looks great. I can make those updates if you'd like.
@Ivandemidov00 can you sign your commits next time please? (if you're comfortable with git rebase you can push -f that would be good but don't worry if not) sorry keep forgetting to remind you and you've contributed quite a bit already, we're very grateful for that 💯 edit also if you want to we'd love to have you on slack.nats.io #dotnet channel as well please feel free to drop in and say hi :o) |
Thanks @Ivandemidov00 ! This looks good to me. |