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

I think check lists should be their own thing. #5

Open
gdey opened this issue Jan 26, 2018 · 1 comment
Open

I think check lists should be their own thing. #5

gdey opened this issue Jan 26, 2018 · 1 comment

Comments

@gdey
Copy link
Owner

gdey commented Jan 26, 2018

A checklist should be the last element in a list.

•••[] This is a sublist.

Also, to simplify the ordered list we should just support the '#' character.

@gdey gdey changed the title I think check lists should be there own thing. I think check lists should be their own thing. May 29, 2019
@gdey
Copy link
Owner Author

gdey commented Dec 26, 2019

When implementing the parser for this came across another issue. And think it make sense to treat list like block elements:

§§ Lists as blocks

Should lists be a block. There are some interesting
issues that arise from lists.

  1. How/when are they terminated?
  2. How do you control numbering styling?
  3. Should a list be split across pages?

All of these are difficult to answer with the current
layout of lists. However, if a list as a block, with the
body being the list text. The headers of the block could
house additional parameters and styling options.

e.g:

«code | lang : gdtxt ;
\« list | type : ordered | page-break: keep-together ;
• How/when are they terminated?
• How do you control numbering styling?
• Should a list be split across pages?

»

• This make's it easy to change between numbered
and bullet lists.
• checkbox would still be determined by adding [\[\]]
next to the [].
• parser is simplified as it's a block with a special handler
for the body?

Cons of this approach:

• arguably harder to read.
• more to type

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