How are existing conversions' narration documents rendered?

Open
#487 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
backend

Research direction

Read the conversion storage and synchronization code, then trace the narration rendering entry point to see how existing conversions are handled. Document whether stored sanitized HTML remains a fallback or is passed through the new renderer, and identify what selects the path. Done means the behavior and the path-selection rule are explained clearly; the issue names no files or tests to start from.

Written by the indexing model from the issue text.

Description

wayfinder:grilling

Question

Existing conversions store only sanitized HTML and their synchronization units, no selected HTML. Do they keep serving their stored HTML as a fallback, or does the new renderer render that sanitized HTML (a subset of the markup) so that presentation changes reach them too? What marks which path a conversion takes?

Dominant language
TypeScript
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 patricktree/cup

All issues in patricktree/cup

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.