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

What is the best way is to determine, if the syntax that I would like to add is not conflicting with any other existing extension. #449

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

Originally created by @olenitsj on GitHub (Apr 1, 2021).

I am working on an extension and I would like to know if my syntax won't be conflicting with any other extension.
What is the best way to achieve that?

Originally created by @olenitsj on GitHub (Apr 1, 2021). I am working on an extension and I would like to know if my syntax won't be conflicting with any other extension. What is the best way to achieve that?
claunia added the question label 2026-01-29 14:37:03 +00:00
claunia commented 2026-01-29 14:37:05 +00:00
Author
Owner
Copy Link

@xoofx commented on GitHub (Apr 3, 2021):

There is no easy way outside of the project itself as you figured out in #538.
We would have to ship the tests as a separate NuGet package in order to support that scenario.

@xoofx commented on GitHub (Apr 3, 2021): There is no easy way outside of the project itself as you figured out in #538. We would have to ship the tests as a separate NuGet package in order to support that scenario.
claunia commented 2026-01-29 14:37:06 +00:00
Author
Owner
Copy Link

@MihaZupan commented on GitHub (Apr 3, 2021):

If you have concrete examples of syntax in mind, you could ask for feedback on the https://talk.commonmark.org/ forum

@MihaZupan commented on GitHub (Apr 3, 2021): If you have concrete examples of syntax in mind, you could ask for feedback on the https://talk.commonmark.org/ forum
claunia commented 2026-01-29 14:37:08 +00:00
Author
Owner
Copy Link

@olenitsj commented on GitHub (Apr 4, 2021):

Thank you for your responses I will look into the proposed solution.

Would the following spec configuration in SpectFileGen result in enabling ALL extensions?

new Spec("Forms", "FormsSpecs.md", "advanced+pipetables+gfm-pipetables+footnotes+attributes+emphasisextras+hardlinebreak+gridtables+customcontainers+definitionlists+emojis+abbreviations+listextras+mathematics+bootstrap+figures+medialinks+smartypants+autoidentifiers+tasklists+diagrams+nohtml+yaml+autolinks+jiralinks+globalization+forms"),

@olenitsj commented on GitHub (Apr 4, 2021): Thank you for your responses I will look into the proposed solution. Would the following spec configuration in SpectFileGen result in enabling ALL extensions? new Spec("Forms", "FormsSpecs.md", "advanced+pipetables+gfm-pipetables+footnotes+attributes+emphasisextras+hardlinebreak+gridtables+customcontainers+definitionlists+emojis+abbreviations+listextras+mathematics+bootstrap+figures+medialinks+smartypants+autoidentifiers+tasklists+diagrams+nohtml+yaml+autolinks+jiralinks+globalization+forms"),
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 question
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#449
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?