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

Option to parse basic markdown vs extended flavors #6

Open
2colours opened this issue Feb 2, 2023 · 0 comments
Open

Option to parse basic markdown vs extended flavors #6

2colours opened this issue Feb 2, 2023 · 0 comments

Comments

@2colours
Copy link

2colours commented Feb 2, 2023

Hi,

this issue is inspired by converting README.md files of Raku modules (to pod6). Since GH itself uses markdown, I'm gonna show the raw text, its expected formatting (by simply adding it to my comment) and the actual formatting (experienced by converting the pod6 back to markdown):

Input:

#### new(Str $xml, :$filename)

Expected output:

new(Str $xml, :$filename)

Actual output:

new(Str xml, :filename)

By the way, this is similar to the formatting that show up in PR's on github: $'s have special meaning to those as well.

Overall, it would be great to be able to specify what sort of Markdown the input should be interpreted as, and generate the output based on that.

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

1 participant