Byron/pulldown-cmark-to-cmark

Is it possible to write back code block backtick count to original?

Open

#20 opened on Aug 4, 2020

View on GitHubContributor guide
 (31 comments) (1 reaction) (0 assignees)Rust (46 forks)auto 404
good first issuehelp wanted

Repository metrics

Stars
 (60 stars)
PR merge metrics
 (Avg merge 35m) (1 merged PR in 30d)

Description

After #17, #18, code block backtick count is configurable. However, there is another problem.

Now let's consider such senario like below:

ex.) https://github.com/yumetodo/markdown_img_url_editor_rust/blob/master/src/lib.rs#L74

  1. Parse markdown file with pulldown-cmark
  2. Edit somewhare.
  3. Write back to markdown using pulldown-cmark-to-cmark

In this case, there is nothing to emulate block backtick count.

As a result, currently, when just bypass pulldown-cmark to pulldown-cmark-to-cmark, input and output is not equal.

Contributor guide

Research direction
Investigate how pulldown cmark represents code blocks and propagate the backtick count to the conversion process.
Tech stack
rust
Domain
tooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50