Closed dux closed 4 years ago
I think feature requested they need to be approved first in https://github.com/haml/haml
ok, but why? This does not brake compatibility.
Because Hamlit only implements the features of haml.
Le lun. 27 juil. 2020 à 12:57, Dino Reić notifications@github.com a écrit :
ok, but why? This does not brake compatibility.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/k0kubun/hamlit/issues/159#issuecomment-664323430, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA2KLEIAJ5FH7DTYNRTVGJDR5VMQ3ANCNFSM4PIUGJ7Q .
@WaKeMaTTa is right. One of the reasons is that Hamlit shares the same parser as Haml, and not using the exact same parser would increase maintenance cost of Hamlit. So at least syntax-level features like this should be proposed and implemented in Haml to avoid diverging the parser part.
Thanks for filing https://github.com/haml/haml/issues/1037! Please feel free to reopen this issue once it's merged.
The same it is implemented in Svelte https://github.com/sveltejs/svelte/issues/90
It would be nice, if we would be able to write
and not as now
I suggest not to play smart, just if for produces
blank? - true
, useelse
block.Added to https://github.com/haml/haml/issues/1037 as well.