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

Add feature to show checkboxes or tasklists as in GitHub #218

Open
dtchanpura opened this issue Jul 19, 2018 · 4 comments
Open

Add feature to show checkboxes or tasklists as in GitHub #218

dtchanpura opened this issue Jul 19, 2018 · 4 comments
Labels

Comments

@dtchanpura
Copy link

dtchanpura commented Jul 19, 2018

GitHub markdown supports creation of checkboxes by writing [ ] (space inside square brackets) and selected checkbox by [x] (x inside square brackets)

Just like as follows

- [ ] not selected
- [x] selected

Reference: https://blog.github.com/2014-04-28-task-lists-in-all-markdown-documents/

@theBusterben
Copy link

i totally support this feature to be added, i use it all the time for taking notes.
I still have to type this to make it appear though

<ul>
<li><input type="checkbox" disabled> foo</li>
<li><input type="checkbox" disabled checked> bar</li>
<li><input type="checkbox" disabled> baz</li>
</ul>

If this feature is going to be implemented, i would also like to suggest crossing off the checkbox to be made also possible in the preview window

@fabiocolacio
Copy link
Owner

I agree that this is a nice feature to add. We use scidown, as a markdown parser, so you might consider opening this issue there also, but I may implement this myself if I can find the time.

@smithfred
Copy link

Would be better to support the full set of GFM extensions if possible, since it's a widely used set of extensions (and is fully specified against CommonMark).

@stefs
Copy link

stefs commented Jul 8, 2022

Here is the relevant scidown issue: Mandarancio/scidown#7
However scidown seems to be unmaintained/abandoned. The last released version is 4 years old.
Maybe it is better to switch to a different parser because of this.

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

No branches or pull requests

5 participants