New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FeatureRequest: Allow Parameters from settings.json file for compile functions #3428
Comments
Is this the settings from VS Code? |
yes. just the casual settings.json file in .vscode directory. we check it into git to provide every dev the same experience (same cops, ruleset and compile options). |
Got it. How would you determine who wins? Parameters or settings? What is your suggested implementation? And what about AL-Go - would we support the same there? |
on Implantation i see three possibilities: 1. Use two parameter sets 2. Load Settings as default 3. Use an Additional Parameter I think option two is not a real option :) for the sake of completeness, it must also be said that we can only use default
Hard to tell since i do not use AL-Go on daily base, just playing around... |
3 would also be my favorite. How would you determine from where to load the vs code settings file? |
Describe the issue
We as well as other partners use the settings from the settings.json in their build pipelines.
Instead of having to parse the settings ourselves, we could implement this option directly in the corresponding cmdlets as an alternate parameter set.
This should be implemented for
Compile-AppInBcContainer
andCompile-AppWithBcCompilerFolder
.Params whe can use from
settings.json
:I could provide a pull request. But I would like to clarify first so that I don't have to do any unnecessary work.
What do you think about this?
The text was updated successfully, but these errors were encountered: