starred/markdig
1
0
Fork 0
mirror of https://github.com/xoofx/markdig.git synced 2026-02-09 05:49:12 +00:00
Code Issues 690 Packages Projects Releases 20 Wiki Activity

Add support for GitHub Markdown Alerts #659

New Issue
Closed
opened 2026-01-29 14:42:17 +00:00 by claunia · 3 comments
claunia commented 2026-01-29 14:42:17 +00:00
Owner
Copy Link

Originally created by @xoofx on GitHub (Feb 20, 2024).

See https://github.com/orgs/community/discussions/16925

> [!NOTE]  
> Highlights information that users should take into account, even when skimming.

> [!TIP]
> Optional information to help a user be more successful.

> [!IMPORTANT]  
> Crucial information necessary for users to succeed.

> [!WARNING]  
> Critical content demanding immediate user attention due to potential risks.

> [!CAUTION]
> Negative potential consequences of an action.

rendered as:

Note

Highlights information that users should take into account, even when skimming.

Tip

Optional information to help a user be more successful.

Important

Crucial information necessary for users to succeed.

Warning

Critical content demanding immediate user attention due to potential risks.

Caution

Negative potential consequences of an action.

Originally created by @xoofx on GitHub (Feb 20, 2024). See https://github.com/orgs/community/discussions/16925 ```md > [!NOTE] > Highlights information that users should take into account, even when skimming. > [!TIP] > Optional information to help a user be more successful. > [!IMPORTANT] > Crucial information necessary for users to succeed. > [!WARNING] > Critical content demanding immediate user attention due to potential risks. > [!CAUTION] > Negative potential consequences of an action. ``` rendered as: > [!NOTE] > Highlights information that users should take into account, even when skimming. > [!TIP] > Optional information to help a user be more successful. > [!IMPORTANT] > Crucial information necessary for users to succeed. > [!WARNING] > Critical content demanding immediate user attention due to potential risks. > [!CAUTION] > Negative potential consequences of an action.
claunia added the enhancementPR Welcome! labels 2026-01-29 14:42:17 +00:00
claunia commented 2026-01-29 14:42:17 +00:00
Author
Owner
Copy Link

@jorge-moreira commented on GitHub (Feb 22, 2024):

Hi Alexandre,

The objective here is to support a new type of block (i.e. AlertBlock) with it's own parser and renderer?
For the parser I would say that there's no doubt on what to do, although for the renderer I've some doubts on how we would support this to be rendered in html.

I'll be glad to help on.

@jorge-moreira commented on GitHub (Feb 22, 2024): Hi Alexandre, The objective here is to support a new type of block (i.e. AlertBlock) with it's own parser and renderer? For the parser I would say that there's no doubt on what to do, although for the renderer I've some doubts on how we would support this to be rendered in html. I'll be glad to help on.
claunia commented 2026-01-29 14:42:19 +00:00
Author
Owner
Copy Link

@xoofx commented on GitHub (Mar 4, 2024):

Added a tentative PR #776 to implement this feature.

@xoofx commented on GitHub (Mar 4, 2024): Added a tentative PR #776 to implement this feature.
claunia commented 2026-01-29 14:42:20 +00:00
Author
Owner
Copy Link

@xoofx commented on GitHub (Mar 4, 2024):

The objective here is to support a new type of block (i.e. AlertBlock) with it's own parser and renderer? For the parser I would say that there's no doubt on what to do, although for the renderer I've some doubts on how we would support this to be rendered in html.

I'll be glad to help on.

Forgot to respond, as I was reading your question yesterday, and I started to play with a parser to see how problematic it would be to implement it and saw that it was in the end relatively small, so decided to complete the implementation. So, my apologies if I took over and thanks for the proposal for helping, I appreciate. 🙂

@xoofx commented on GitHub (Mar 4, 2024): > The objective here is to support a new type of block (i.e. AlertBlock) with it's own parser and renderer? For the parser I would say that there's no doubt on what to do, although for the renderer I've some doubts on how we would support this to be rendered in html. > > I'll be glad to help on. Forgot to respond, as I was reading your question yesterday, and I started to play with a parser to see how problematic it would be to implement it and saw that it was in the end relatively small, so decided to complete the implementation. So, my apologies if I took over and thanks for the proposal for helping, I appreciate. 🙂
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
extension
Hacktoberfest
invalid
PR Welcome!
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label enhancement PR Welcome!
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/markdig#659
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?