From d28bb0f5a698557183cd5f7a6b6cddd83ca33cc0 Mon Sep 17 00:00:00 2001 From: shub12388y Date: Sat, 21 Jun 2025 20:47:39 +0530 Subject: [PATCH] fix the syntax --- www/blog/_posts/2024-10-03-memoization-in-hmpl.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/www/blog/_posts/2024-10-03-memoization-in-hmpl.md b/www/blog/_posts/2024-10-03-memoization-in-hmpl.md index 0a15ac7..cfc2c39 100644 --- a/www/blog/_posts/2024-10-03-memoization-in-hmpl.md +++ b/www/blog/_posts/2024-10-03-memoization-in-hmpl.md @@ -73,7 +73,7 @@ The main disadvantage, of course, is the extra allocation of memory for storing Since HTML is a template language for displaying the user interface from the server to the client, http requests will need to be memorized. Accordingly, the intended result will be the preservation of HTML markup. Here is an example of how HMPL works: ```javascript -const newDiv = compile( +const newDiv = hmpl.compile( `
{% raw %}{{ src: "/api/getTheSquareRootOf256", after: "click:button" }}{% endraw %}
@@ -88,7 +88,7 @@ So, the problem with previous versions is that a new element was constantly put Specifically to optimize this process, an additional field was introduced, which is called `memo`. ```javascript -const newDiv = compile( +const newDiv = hmpl.compile( `
{% raw %}{{ src: "/api/getTheSquareRootOf256", memo:true, after: "click:button" }}{% endraw %}