debugger: some improvements in configuration handling #2364
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)configuration.schema.json
updated if new parameters are added.What kind of change does this PR introduce?
Added some small fix in how the debugger configuration is handled:
debug.server.openocd.scripts.N
.debug.server.openocd.script
directive is ignored if is together with thedebug.server.openocd.scripts.N
.What is the current behavior?
debug.server.openocd.scripts.N
sequence was truncated at the first non-consecutive item.script
andscripts
were concatenated in the resulting config.What is the new behavior?
debug.server.openocd.scripts.N
sequence is not truncated even if the items are non-consecutive.scipt
andscripts
are mutually-exclusive in the config with priority given toscripts
.Does this PR introduce a breaking change, and is titled accordingly?
Other information