astynax / hemmet Goto Github PK

For now there is only a couple of preprocessors for some genenerators. But it will be nice to have a way to customize the output: pretty-printing, size of indentation. It can be a mini-language like "key=val,key=val|" that will prepend the template itself.

Add text braces

Service block example:

<div class="menu">
  <div class="menu-item menu__menu-item">
    <div class="menu-item__label menu-item_disabled_t">
...

Here menu-item is a service block mixed with element.

Add a scrollable sidebar with a grammar of the current template language.

I'm thinking about these variants:

• text-builder as a replacement for the current padding and printing.
• prettyprinter as a way more generic solution that will help to drop any manual padding and low-level text manipulations.

Add Elm generator. It will be perfect if generated code will look like elm-formated one.

Add a new generator for the kotlinx.html.

Add a "climb up" operator. Is this good idea, btw?

Add multiplication

For some tags like <img/> and <br/> we need to have a way to render them without corresponding closing tags. I see that as an optional / (zero or one) char at the end of the tag name. All the renders should then handle such "flag" appropriately.

I guess this would do the trick: https://github.com/fernandrone/linelint#GitHub-Actions

Expression is: (a>b)+div

Megaparsec says:

unexpected '+'
expecting end of input

Add generators for Shakespearean Templates

• Hamlet
• Cassius
• Lucius?

It should be possible to support variables for any of these generators.

Example, working in Emmet: a.b#a.c

Implement a non-BEM syntax for HTML (DOM). This one should mimic BEM tree but shouldn't do any additional generation as BEM does.

Currently these GHC versions are not supported. That would be nice to have them supported.

Make project a cabal-based by default:

• configure project,
• rework package.yaml to .cabal,
• freeze deps (?)
• add hie.yaml.

It would be nice to have CI checking that tests are all working.

Если написать имя тега, например:

<:block>span.elem

то получим комбинатор с именем span

span "block__elem" $ pure ()

А надо spanc_. По соглашению, имена функций для генерации тегов состоят из имя_тега <> "c_"

_ из react-flux, а c говорит, что функция принимает аргументом Class.