From d9ece62746154db0b9e0e43d88c087a63eceaf16 Mon Sep 17 00:00:00 2001 From: Madalin Grigore-Enescu Date: Wed, 31 Aug 2022 22:53:46 +0300 Subject: [PATCH] Modified README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b2c1513..b8d56f2 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,7 @@ The need for erlte arose while using good old sgte in various web applications. ## Limitations - Only JavaScript static import declarations are supported. - CSS @import rules work fine only with file strings (no list of media queries or url are supported). -- Erlte "compiler" is far away from a full parser. It behaves well for most scenarios, but some corner cases may exist. As long as you use single line imports and you don't nest unescaped comments or imports in strings, you should be fine. +- erlte "compiler" is far away from a full HTML/JS/CSS parser. It behaves well for most scenarios, but some corner cases may exist. As long as you use single line imports and you don't nest unescaped comments or imports in strings, you should be fine. - erlte does not support any conditionals or pseudocode and will probably never do. For some, this is a limitation, for me, it's a feature. The price of implementing this will be a much slower rendering speed. I also don't like polluting my HTML templates with spaghetti code. We have JavaScript for that. ## Alternatives