Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Markdown not properly rendered #169

Open
leohhhn opened this issue May 6, 2024 · 1 comment
Open

Markdown not properly rendered #169

leohhhn opened this issue May 6, 2024 · 1 comment
Assignees

Comments

@leohhhn
Copy link
Contributor

leohhhn commented May 6, 2024

Description

I realized that some markdown is not properly rendered:

---
title: Sending native coins in Gno
section: Chain
---

By using the Banker module, you are able to send native Gno coins, such as `ugnot` 
from one address to another. Each realm can inject the Banker module into the Gno
runtime and can cast it into a specific type of Banker. Each Banker type has its 
own set of access rights for security reasons. Banker types are the following:

- `BankerTypeReadonly` - read-only access to coin balances,
- `BankerTypeOrigSend` - full access to coins sent with the transaction that 
calls the banker,
- `BankerTypeRealmSend` - full access to coins that the realm itself owns,
including the ones sent with the transaction,
- `BankerTypeRealmIssue` - able to issue new coins.

As is currently on
Screenshot 2024-05-06 at 14 44 24

While the break lines should not affect the render, like below:
Screenshot 2024-05-06 at 14 45 05

@alexiscolin
Copy link
Member

alexiscolin commented May 27, 2024

@leohhhn This happens because you use a list symbol just after another parsed inline-block (the code one). It's a bug due to the markdown parser (markdown-to-jsw) that is known... You can try and you will have the same result here: https://markdown-to-jsx.quantizor.dev/

I may try to use another parser but, to complete your task quick, the easiest thing to do would be to rewrite the md content by avoiding this "-" symbol. You can use the long dash or a : or by adding a non-breaking space   between code and dash instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants