Which inline markup does the narration document keep?

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
typescript
Domain
backend

Research direction

The issue names no files or tests. Start by locating where inline markup is kept or flattened in the narration document pipeline, then review how its current behavior handles the listed tags. Done means deciding which inline elements to preserve or map and documenting that policy; the issue does not specify the desired choice.

Written by the indexing model from the issue text.

Description

wayfinder:grilling

Question

Today a, em, strong, code and br are kept while b, i, u, s, mark, sub/sup, span and others are flattened to text, so <b> loses its bold while <strong> keeps it. Which inline markup should the narration document keep: map b/i to strong/em or flatten all emphasis, keep code or flatten it, and does anything of the flattened rest (sub/sup, s/del, q, abbr) deserve to stay?

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.