Respect the EditorConfig rules

[jbampton]

Hey @BaseMax see the editor config file and make sure your VSC respects its rules.

https://github.com/SalamLang/Salam/blob/main/.editorconfig

Shell scripts are currently indented with tabs !

https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig

refs #970 where I fixed the shell formatting

The Super-Linter shell format check fails when you use spaces for indents.

Make sure you have the EditorConfig plugin installed and working

Tagging @BDadmehr0 here too

[BaseMax]

Which one? @jbampton

[jbampton]

Yes the 11 million downloads one the top one

[BDadmehr0]

Hi, I have a question: Are we forced to use plugins in VS Code?
I know that these plugins are available in most editors, but I researched and found out that it’s possible to use CLI tools and some commands to create automated tools for tasks like converting spaces to tabs. Tools like:

• editorconfig-cli
• shfmt
• lint-staged + Super-Linter

For example:

Finding all files:

find . -type f -name "*.sh"

Output:

./build-linux.sh
./build-webassembly.sh
./build/styles/run_all.sh
./build/tags/run_all.sh
./build/data/styles/values/run_all.sh
./build/data/styles/run_all.sh
./build/data/tags/values/run_all.sh
./build/data/tags/run_all.sh

These files can then be passed to CLI formatters.

[jbampton]

Hi @BDadmehr0 no you are not forced you can choose your own.

I don't use VSC or Windows.

But @BaseMax uses VSC

[jbampton]

refs #885