Skip to content

docs: resource/op sanitizers off by default in deno test (2.8)#3072

Open
lunadogbot wants to merge 1 commit intodenoland:mainfrom
lunadogbot:docs/2.8-test-sanitizers-default
Open

docs: resource/op sanitizers off by default in deno test (2.8)#3072
lunadogbot wants to merge 1 commit intodenoland:mainfrom
lunadogbot:docs/2.8-test-sanitizers-default

Conversation

@lunadogbot
Copy link
Copy Markdown

Summary

Documents the default change in Deno 2.8 (denoland/deno#33250): sanitizeOps and sanitizeResources are now false by default.

  • Adds an info admonition at the top of the Sanitizers section in runtime/fundamentals/testing.md.
  • Reframes the per-test snippets to opt in rather than opt out.
  • New "Enabling sanitizers globally" subsection documents the four global opt-in mechanisms (per-test → module-level Deno.test.sanitizer() → CLI flags → env vars → deno.json) with their precedence order.
  • Exit sanitizer is left unchanged because its default did not change.

Test plan

  • deno task serve — Sanitizers section renders, anchors resolve.
  • If the upstream PR's API names shift before merge (e.g. Deno.test.sanitizer() rename), refresh accordingly.

Updates the Testing guide for the default change in Deno 2.8: the
resource and async-op sanitizers are now off by default. Adds an info
admonition near the Sanitizers heading and a new "Enabling sanitizers
globally" subsection documenting the per-test, module-level
(\`Deno.test.sanitizer()\`), CLI-flag, env-var, and \`deno.json\`
opt-ins, with their precedence order. The exit sanitizer is unchanged.

Refs denoland/deno#33250
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.

1 participant