You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, when you have a chained configuration, you might want to override/null a setting for a child. lets say you have something like this in the top-level config.
Assume that the configuration"Attach Network Core" has its own "svdFile" specification. The parent is specifying that while launching the child, ignore the setting for "svdFile". The "loadFiles" being an empty set means do not program the device -- ie you can have a child configuration of type "launch" and start debug without re-programming because the parent took care of that already. I have two issues.
First I am assuming that this is possible without too much trouble. I will find out soon
I have no idea on how to make IntelliSense work for the "overrides". There is so much duplication in package.json already. If anyone knows any VSCode tricks to make life easier, please let me know.
There may be other things like "post..." settings that are different or not applicable to child configurations. The goal is to use existing configurations so that they can be used stand-alone and also be usable in a chained configuration without having to duplicate an entire configuration for minor changes.
The "svdFile" example above may be a bad example because what you might want is to refresh the peripherals regardless of which core halted. But that should be a separate topic.
Btw, the "loadFile" already works this way if you want to avoid programming for any configuration without having to do a whole override....
The text was updated successfully, but these errors were encountered:
Sometimes, when you have a chained configuration, you might want to override/null a setting for a child. lets say you have something like this in the top-level config.
Assume that the configuration
"Attach Network Core"
has its own"svdFile"
specification. The parent is specifying that while launching the child, ignore the setting for"svdFile"
. The"loadFiles"
being an empty set means do not program the device -- ie you can have a child configuration of type "launch" and start debug without re-programming because the parent took care of that already. I have two issues.There may be other things like
"post..."
settings that are different or not applicable to child configurations. The goal is to use existing configurations so that they can be used stand-alone and also be usable in a chained configuration without having to duplicate an entire configuration for minor changes.The
"svdFile"
example above may be a bad example because what you might want is to refresh the peripherals regardless of which core halted. But that should be a separate topic.Btw, the
"loadFile"
already works this way if you want to avoid programming for any configuration without having to do a wholeoverride....
The text was updated successfully, but these errors were encountered: