Releases: HexmosTech/Lama2
v1.6.1
v1.6.0
v1.5.9
Adding documentation
- Minor code refactor
- Linking Lama2Code examples in documentation
What's Changed
- Origin/l2lsp by @lovestaco in #36
- Adding documentation for lsp, documentation by @lovestaco in #37
Full Changelog: v1.5.7...v1.5.9
v1.5.8
Adding LSP support to Lama2
Previous Functionality:
- In version v1.5.7, the suggestenvs feature was using command line driven request, ex:
l2 -e="searchquery"
What's New:
- In current version we have converted the feature to use a custom LSP method called
suggest/environmentVariables
. - Extensions can simply call this method using relevant JSON RPC params
Request body
{
"jsonrpc": "2.0",
"id": 2,
"method": "suggest/environmentVariables",
"params": {
"textDocument": {
"uri": "file:///home/Lama2/elfparser/ElfTestSuite/root_variable_override/api/y_0020_root_override.l2"
},
"position": {
"line": 1,
"character": 2
},
"searchQuery": "<your_search_string>"
}
}
Replace your_search_string
with the desired search query, and the method will output environment variables based on that string.
Enhanced testing: Additional test cases have been introduced, and existing ones have been updated to support these changes.
Thank you for choosing our binary.
We appreciate the continued support and contributions from our community.
Your feedback and involvement are what make this project thrive!
Related vsc extension release
Releaese in progress
Checkout PR
Full Changelog: v1.5.7...v1.5.8
v1.5.7
v1.5.6
Enhanced Environment Variable Support
Previous Functionality:
- In version v1.5.1, the command l2 -e generated a JSON of the environment variables l2env and l2config.env.
What's New:
-
The command has been updated for better flexibility.
-
To fetch all environment variables as JSON, use:
l2 -e='' <filepath>
- To search for specific environment variables based on a string and output them, use:
l2 -e=your_search_string <filepath>
Replace your_search_string with the desired keyword, and the command will now output environment variables based on that string.
- Enhanced testing: Additional test cases have been introduced, and existing ones have been updated to support these changes.
Thank you for choosing our binary.
We appreciate the continued support and contributions from our community.
Your feedback and involvement are what make this project thrive!
Documentation
https://hexmos.com/lama2/tutorials/editor.html#providing-environment-variable-autocompletion
Usage
https://www.loom.com/share/34ecffdfb62749f0bdece994c49bf61a
Related vsc extension release
What's Changed
- Issue: HexmosTech/Lama2Code#17
- Origin/suggest relevant env's by @lovestaco in #32
Full Changelog: v1.5.5...v1.5.6
v1.5.5
Earlier, code generation used to work only for single stage l2 files. Now it functions fine on multi-stage files (mostly). The results are not perfect, but still useful enough to warrant a release.
What's Changed
Full Changelog: v1.5.0...v1.5.2
v1.5.1
When l2config/ l2env was absent, the l2--env <l2fielpath>
command was breaking, added fix to that.
Adding documentation and examples for the same.
What's Changed
- Root var l2configenv fix by @lovestaco in #26
Full Changelog: v1.5.0...v1.5.1
v1.5.0
Support for Root variables
- Variables can be defined in a single file at the Project root in
l2config.env
. - New option
(-e/ --env)
for l2 command to generate JSON of Root and Local variables.l2 --env <l2filepath>
What's Changed
- Global variable support and Generate env JSON option by @lovestaco in #24
New Contributors
- @lovestaco made their first contribution in #24
Full Changelog: v1.4.3...v1.5.0