Global variable support and Generate env JSON option

[lovestaco]

What type of MR is this?

• [x] 🍕 Feature
• [ ] 🐛 Bug Fix
• [x] 📝 Doc Update
• [ ] 🎨 Style
• [x] 🧑‍💻 Code Refactor
• [x] 🔥 Performance Improvements
• [ ] ✅ Test
• [ ] 🤖 Build
• [ ] 🔁 CI
• [ ] ⏩ Revert

Description

This MR adds the feature of supporting global variables. Edit1:

• L2 can now fetch variables declared in l2config.env which can be in the parent directory.

• l2config.env is searched for, from the present directory to all its ancestors (upto /).

• A directory may have both l2.env AND l2config.env

Edit2:

• Added a new option for l2command l2 --env <l2FilePath>.
• L2 will output a JSON of environment variables with metadata from l2config.env and l2.env.
• Added this feature so frontend i.e. IntelliJ/ VScode suggesting variables can be done in a quicker and more detailed high-quality way.

  {
  "KARMA_LOCAL_URL": {
  "src": "l2configenv",
  "val": "http://127.0.0.1:8000"
  },
  "PARSE_URL_LOCAL": {
  "src": "l2env",
  "val": "http://localhost:1337/parse"
  }
  }

Important code file to start Code Review from

controller.go

Added tests?

• [ ] 👍 yes
• [ ] 🙅 no, because they aren't needed
• [x] 🙋 no, because I need help

Added to documentation?

• [x] 📓 l2format.md
• [x] 📓 architecture.md
• [x] 📜 preprocess.md
• [x] 📜 examples.md

[shrsv]

After every documentation change - we are supposed to run the following and commit all resultant files:

mkdocs:
    cd docs/Lama2; ./build.sh

Anyway - wait till my overall review finishes, then you can do this.

[shrsv]

Remaining comments - I think we still do not have functionality for obtaining the variable suggestions from VSCode (using some CLI switch - pls make proposals). That can be added to this MR itself.

[shrsv]

In general - nice first MR :+1:

[shrsv]

Also - we must add test case(s) for this new logic.

[shrsv]

L2 can now fetch variables declared in l2config.env which can be in the parent directory.

L2 will first fetch the variables from the l2config.env which can be in the parent directory and
then fetch the variables from l2.env from the present dir.

The description has to be more precise.

1. l2config.env is searched for, from the present directory to all its ancestors (upto /). Yes, a directory may have both l2.env AND l2config.env (make sure this is so)

[shrsv]

Also - we must add test case(s) for this new logic.

This has not been addressed @lovestaco

[lovestaco]

Also - we must add test case(s) for this new logic.

This has not been addressed @lovestaco

https://github.com/HexmosTech/Lama2/blob/globalvar-l2configenv/elfparser/ElfTestSuite/root_variable_override