When using the incrementBuildNumber option, all PDXInfo keys are output to the PDXInfo file, including optional ones that may have originally not been included. In my case, I don't have the ContentWarning fields in the file, but they get added anyway when my project builds, as follows:
Perhaps this could be fixed by replacing this line with something like this:
const lines = [];
for (const key of keyOrder) {
const value = pdxInfo[key];
if (value !== undefined) {
lines.push(`${key}=${value}`);
}
}
or with a schema change. However due to my limited familiarity with the TypeScript ecosystem I ran into issues running tests for the extension as well as getting around an error from a pre-commit hook, so I couldn't quite get to verifying and/or PRing in any of those options. I'm happy to leave it to the experts if this is deemed a valid issue :)
When using the
incrementBuildNumber
option, all PDXInfo keys are output to the PDXInfo file, including optional ones that may have originally not been included. In my case, I don't have theContentWarning
fields in the file, but they get added anyway when my project builds, as follows:Perhaps this could be fixed by replacing this line with something like this:
or with a schema change. However due to my limited familiarity with the TypeScript ecosystem I ran into issues running tests for the extension as well as getting around an error from a pre-commit hook, so I couldn't quite get to verifying and/or PRing in any of those options. I'm happy to leave it to the experts if this is deemed a valid issue :)