Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

PDF rendering issues in Cheat Sheets

Open
#3,420 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
documentation

Research direction

Start with the Cheat Sheets PDF rendering for the Control Flow Analysis and Expressions examples described in the issue, and reproduce the output. Done means the code samples preserve vertical quotation marks and show spacing between equation signs in the generated PDF.

Written by the indexing model from the issue text.

Description

🔎 Search Terms

Cheat Sheets

🕗 Version & Regression Information

(not version related)

⏯ Playground Link

No response

💻 Code
// Your code here
🙁 Actual behavior

On page Control Flow Analysis, section If Statements, code sample if (typeof input === "string", the PDF is rendered as if (typeof input ═══ “string” (the equation signs are not separated by spaces, the double quotation marks are typographic "66 and 99" versions instead of ASCII "...").
The code sample if ("error" in input") is rendered as if (“error” in input) (double quotation issues). In section Expressions, the code sample (typeof input === "string" && is rendered as (typeof input ═══ "string" && (spaces not showing between equation signs).

🙂 Expected behavior

Please use vertical quotation marks instead of typographic ones. Insert spaces between equation signs or increase spacing.

Additional information about the issue

No response

Dominant language
TypeScript
Stars
2.6k
Forks
1.5k
Avg merge
2d 12h
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/TypeScript-Website

All issues in microsoft/TypeScript-Website

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.