liran-funaro / sphinx-markdown-builder / 43205038641

100%

push

github

Size code fences so backticks in code cannot break out (#133)

## Summary

Inline literals always used one backtick and literal/doctest blocks
always used three, so code containing backticks closed its own fence
early. The fence is now one backtick longer than the longest backtick
run in `node.astext()` (at least 1 inline, at least 3 for blocks).
Inline code that starts or ends with a backtick gets one space of
padding on each side, which CommonMark strips. The closing marker lives
in a new `ContextStatus.code_fence_end` field, so the depart uses the
same fence as the visit (RULES 5).

## Fixtures

Added to `tests/source/blocks.rst`, after the existing code block:

````rst
Inline: ``a`b`` and ```x```.

.. code-block:: markdown

   ```python
   x = 1
   ```
````

Before:

`````markdown
Inline: `a`b` and ``x``.

```markdown
```python
x = 1
```
```
`````

After (`tests/expected/blocks.md`):

`````markdown
Inline: ``a`b`` and `` `x` ``.

````markdown
```python
x = 1
```
````
`````

## Existing golden output that changes

`tests/expected/ExampleRSTFile.md` already had three inline literals
with backticks, and its expected output recorded the broken rendering.
They are now correct:

```diff
-of the heading for that location as link text, use `:ref:`Anchor Text``
+of the heading for that location as link text, use `` :ref:`Anchor Text` ``
-section that you’re linking to, use `:ref:`specified text<Anchor Text>``
+section that you’re linking to, use `` :ref:`specified text<Anchor Text>` ``
-For example, ```these words``` are formatted in a monospace font when the
+For example, ``` ``these words`` ``` are formatted in a monospace font when the
```

No other golden output changes.

## Commands

- `make lint`: passes (black, flake8, pylint 10.00/10).
- `make test`: passes, 15 passed, coverage 100%.

Closes #115

31 of 31 new or added lines in 2 files covered. (100.0%)

796 of 796 relevant lines covered (100.0%)

4.0 hits per line