Skip to content

Conversation

@Naymi
Copy link

@Naymi Naymi commented Nov 24, 2024

No description provided.

@netlify
Copy link

netlify bot commented Nov 24, 2024

Deploy Preview for testcontainers-node ready!

Name Link
🔨 Latest commit 4059cb9
🔍 Latest deploy log https://app.netlify.com/sites/testcontainers-node/deploys/67433d723f2e7100085b3045
😎 Deploy Preview https://deploy-preview-873--testcontainers-node.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

// JetStream {
it("should start with JetStream ", async () => {
// enable JS
const container = await new NatsContainer().withJS().start();
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is JS a well known acronym for Jetstream for Nats users?

@cristianrgreco cristianrgreco added enhancement New feature or request minor Backward compatible functionality labels Nov 24, 2024
@jonjomckay
Copy link
Contributor

This would be helpful for us - we use JetStream, but we're unable to use NatsContainer at all at the moment, as we can't use withArg with a single parameter.

@cristianrgreco
Copy link
Collaborator

cristianrgreco commented Nov 28, 2024

Hi @jonjomckay, I'm not familiar with NATS. If you were using the NatsContainer and came across a method withJS, would you understand that it is for enabling jetstream, or would withJetStream be better?

@jonjomckay
Copy link
Contributor

@cristianrgreco withJetStream would be clearer to me. JS is probably a bit confusing, especially with this being a JavaScript library!

@cristianrgreco
Copy link
Collaborator

IDK if @Naymi is going to address the issues with the PR, but @jonjomckay if you want this feature then I'd happily accept a PR. A copy of this one is fine with withJS changed to withJetStream, with lint issues addressed.

@jonjomckay
Copy link
Contributor

@cristianrgreco @Naymi I've opened up another PR with the linting and naming fixed: #877

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request minor Backward compatible functionality

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants