We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/nats-io/nats.rs/blob/main/async-nats/examples/jetstream_push.rs https://github.com/nats-io/nats.rs/blob/main/async-nats/examples/jetstream_pull.rs
are pretty much identical (from what I can tell)
do not have duplicate examples (you should just have one)
not relevant
No response
The text was updated successfully, but these errors were encountered:
probably not a defect. However, I did not know what to put this as.
Sorry, something went wrong.
Key difference is that they create different configs, e.g pull::Config vs push::Config, these give different implementations of the internals.
pull::Config
push::Config
Pull example can probably be expanded to showcase fetch etc tho.
Key difference is that they create different configs, e.g pull::Config vs push::Config, these give different implementations of the internals. Pull example can probably be expanded to showcase fetch etc tho.
ah I see... yea was hard for me to tell that was the difference but perhaps I did not look hard enough. wonder if this can be emphasized somehow.
I agree with both of you:
No branches or pull requests
Observed behavior
https://github.com/nats-io/nats.rs/blob/main/async-nats/examples/jetstream_push.rs
https://github.com/nats-io/nats.rs/blob/main/async-nats/examples/jetstream_pull.rs
are pretty much identical (from what I can tell)
Expected behavior
do not have duplicate examples (you should just have one)
Server and client version
not relevant
Host environment
No response
Steps to reproduce
No response
The text was updated successfully, but these errors were encountered: