[FEATURE] - project-local config files

[Mai-Lapyst]

The extension should provide a way to allow for project-local configuration files; propably the easiest way is by supporting ${workspaceFolder} and ${workspaceRoot} in pascal.formatter.engineParameters.

[alefragnani]

Hi @Mai-Lapyst ,

Do you mean make the parameter to support relative paths, right?

Thanks for reporting

[Mai-Lapyst]

This could potentially also help; but I rather ment vs-code's variables: https://code.visualstudio.com/docs/editor/variables-reference. We really only need ${workspaceFolder}; since relative paths dont work well wenn having a multi-root workspace.

[alefragnani]

We are basically describing the same thing, as ${workspaceFolder} represents the base path of the currently opened project. And in a multi-root project, it will be the base path of the root-folder of the focused/active file 😬

[Mai-Lapyst]

Yeah thats what I ment too; sorry for my misunderstanding ^^'

[mmangelsdorf]

@alefragnani I would like to pick up this issue and just wanted to make sure there hasn't been any work done on it yet :)

Please also let me know if there's anything more I should look out for (or read beforehand), being absolutely new to VS Code extension development 🙈

[alefragnani]

Hi @Merlin2001 ,

Feel free to pick upd the issue 😬 .

About VS Code extensions development, I would looking at https://code.visualstudio.com/api/get-started/your-first-extension, with the initial steps to have an extension up and running.

This extension in particular, doesn't have anything special/complicated in terms of APIs, except the DocumentFormattingEditProvider, but you shouldn't need to touch on that. But your should probably look for https://code.visualstudio.com/api/references/vscode-api#WorkspaceConfiguration and if/how to translate variables https://code.visualstudio.com/docs/editor/variables-reference.

Feel free to open the PR, and ping me there if you need any help with it.

Thank you