Skip to content

fix(doc): handle non-ASCII doc lint diagnostics#34626

Merged
littledivy merged 1 commit into
mainfrom
orch/divybot-366
May 31, 2026
Merged

fix(doc): handle non-ASCII doc lint diagnostics#34626
littledivy merged 1 commit into
mainfrom
orch/divybot-366

Conversation

@divybot

@divybot divybot commented May 31, 2026

Copy link
Copy Markdown
Contributor

Summary

  • render doc lint diagnostic highlights using UTF-8 character boundaries
  • cover non-ASCII exported symbols and private type references in doc lint specs

Testing

  • cargo fmt --check
  • git diff --check
  • cargo check -p deno --bin deno

Note: attempted to run the focused deno doc --lint fixture, but building a runnable binary required a separate full codegen pass; the type check completed successfully.

Closes denoland/divybot#366

Render documentation lint highlights using UTF-8 character boundaries so non-ASCII identifiers do not produce invalid diagnostic ranges.

Co-Authored-By: Divy Srivastava <[email protected]>
@littledivy
littledivy merged commit d094bc8 into main May 31, 2026
138 checks passed
@littledivy
littledivy deleted the orch/divybot-366 branch May 31, 2026 16:04
littledivy added a commit to crowlKats/deno that referenced this pull request Jun 10, 2026
## Summary
- render doc lint diagnostic highlights using UTF-8 character boundaries
- cover non-ASCII exported symbols and private type references in doc
lint specs

## Testing
- cargo fmt --check
- git diff --check
- cargo check -p deno --bin deno

Note: attempted to run the focused `deno doc --lint` fixture, but
building a runnable binary required a separate full codegen pass; the
type check completed successfully.

Closes denoland/divybot#366

Co-authored-by: divybot <[email protected]>
Co-authored-by: Divy Srivastava <[email protected]>
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