Markdown: missing or loose findings for fences, ParseInline and nearest-name hints

Open
  • Is something wrong?
#82 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
backend

Research direction

Start by reviewing PR #73 and trace the ::: fence handling, ParseInline, and Nearest hint logic in the repository. Check the tests covering these cases, then add findings or replacements for the listed malformed syntax and tighten the edit-distance bound. Done means each listed case reports the specified error or produces a stricter hint, with tests covering the behavior.

Written by the indexing model from the issue text.

Description

From the PR #73 review:

  • ::: note / :::note is read silently as text, with no finding.
  • An unclosed ::: fence has no Replacement.
  • ParseInline turns a blank-line break into U+2028 silently; spec 3.5 says block syntax is an error there.
  • a**[x]{v}**b reads as literal ** with no finding.
  • The Nearest hint is too loose ({foo} suggests tool); use a stricter edit-distance bound.
Dominant language
C#
Stars
0
Forks
0
Avg merge
1h 43m
Merged PRs (30d)
43

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 sillsdev/SIL.TextEditing

All issues in sillsdev/SIL.TextEditing

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.