feat(experimental:template-language): start an own template language #27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sassman
force-pushed
the
feat/x/custom-templ-language
branch
3 times, most recently
from
696a6a9 to
dd9a0ae
Compare
sassman
force-pushed
the
feat/x/custom-templ-language
branch
3 times, most recently
from
9a825cd to
fa1a43d
Compare
sassman
force-pushed
the
feat/x/custom-templ-language
branch
from
94eedd2 to
179290f
Compare
sassman
force-pushed
the
feat/x/custom-templ-language
branch
from
2e82b49 to
4f1ca62
Compare
The whole reason for this experiment is to get closer to the http plugin template syntax as linked in #5 There the vscode plugin [has this concept of system variables](https://marketplace.visualstudio.com/items?itemName=humao.rest-client#system-variables) that follow the syntax of a mix of expression and function e.g. - {{$randomInt min max}}: Returns a random integer between min (included) and max (excluded) - {{$dotenv [%]variableName}}: Returns the environment value stored in the .env file which exists in the same directory of your .http file. Both examples show that `$<ident>` is similar to a function name and then a variable argument list is passed without any braces like `()`. This experiment focuses on the ability to register functions for this very system variable syntax at compile time in an extensible fashion. done so far: - lexing and parsing of very basic templates with an expression `{{ var }}` - basic runtime to interpret the AST - some tests added - design of a Visitor pattern for the AST yet open - [ ] tests for unhappy path are to less - [ ] runtime is very incomplete yet, `SysVar` hooked functions are missing e.g. `hello {{ $processEnv HOME }}`
Signed-off-by: Sven Kanoldt <[email protected]>
sassman
force-pushed
the
feat/x/custom-templ-language
branch
from
deff5fc to
e8638a9
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #27 +/- ##
===========================================
- Coverage 74.50% 64.23% -10.27%
===========================================
Files 37 43 +6
Lines 957 1110 +153
===========================================
Hits 713 713
- Misses 244 397 +153 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CAUTION! This is an experiment
The whole reason for this experiment is to get closer to the http plugin template syntax as linked in #5
There the vscode plugin has this concept of system variables that follow the syntax of a mix of expression and function e.g.
Both examples show that
$<ident>is similar to a function name and then a variable argument list is passed without any braces like().This experiment focuses on the ability to register functions for this very system variable syntax at compile time in an extensible fashion.
done so far:
{{ var }}yet open
SysVarhooked functions are missing e.g.hello {{ $processEnv HOME }}