Skip to content

Conversation

andyleiserson
Copy link
Contributor

This is useful when running test snippets. Update READMEs including to mention how to do that.

Testing
Adds directed tests.

Squash or Rebase? Squashv

Checklist

  • Run cargo fmt.
  • Run taplo format.
  • Run cargo clippy --tests. If applicable, add:
    • --target wasm32-unknown-unknown
  • Run cargo xtask test to run tests.
  • If this contains user-facing changes, add a CHANGELOG.md entry.

…s called

This is useful when running test snippets. Update READMEs including to
mention how to do that.
@andyleiserson
Copy link
Contributor Author

@crowlKats would be interested in your thoughts here on whether this is an appropriate thing to do in Deno. It would also be possible to do this just in cts_runner and avoid changing the behavior for other applications.

I chose to do it in Deno based on the following note:

After dispatching the event, user agents should surface uncaptured errors to developers, for example as warnings in the browser’s developer console, unless the event’s defaultPrevented is true. In other words, calling preventDefault() on the event should silence the console warning.

But stderr is not exactly analogous to the browser console.

@crowlKats
Copy link
Collaborator

crowlKats commented Sep 27, 2025

yeah this is not something we'd want: we basically never want to print to the terminal from internal logic.

@andyleiserson
Copy link
Contributor Author

Oops, I clicked "sync fork" in the wrong branch in my repo, didn't actually push any changes to this PR.

I will update to change behavior in cts_runner only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants