-
Notifications
You must be signed in to change notification settings - Fork 319
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
[VSC-1573] ensure build directories exist and resolve relative paths #1417
base: master
Are you sure you want to change the base?
Conversation
- Replace forEach with Promise.all for proper async handling - Automatically create build directories using ensureDir - Convert relative paths to absolute using workspace folder as base - Refactor build config access for better readability
Download the artifacts for this pull request: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest we validate that the given path string be validated to separate and support both relative and absolute paths.
commandDictionary[CommandKeys.SelectProjectConfiguration].checkboxState | ||
); | ||
if (projectConfExists) { | ||
if (!projectConf) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
projectConf
doesn't mean is an error. Means the user has not selected a profile at the moment. Even if ESP.ProjectConfiguration.PROJECT_CONFIGURATION_FILENAME
exists.
compileArgs: buildConfig?.compileArgs, | ||
ninjaArgs: buildConfig?.ninjaArgs, | ||
buildDirectoryPath: buildDirPath, | ||
sdkconfigDefaults: (await resolveConfigPaths( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Await is not needed if function is not asynchronous
I've tested this PR with this example config-test project but the build directory resolution is wrong. Generated build directory is Also if I set the path |
Project Configuration Editor related bug: When |
Description
Fixed an issue where relative paths in project configurations were not being handled correctly and build directories were not being created automatically. The extension now properly resolves relative paths to absolute using the workspace folder as the base and ensures build directories exist before build commands are executed.
Fixes #1408
Fixes #1430
Type of change
Steps to test this pull request
Expected behaviour:
How has this been tested?
As described above
Test Configuration:
Checklist