#200 adds the ability to specify variables and tunables as maps of string-valued properties. The allowed set of tunable property names is fixed in an XML configuration file that is packaged in the daffodil-lib artifact.
It should be possible to create a build task that re-writes the package.json file to include schema restrictions on the tunable property names that are derived from that upstream configuration file. Then the built extension could better validate launch.json files that use tunables.
#200 adds the ability to specify variables and tunables as maps of string-valued properties. The allowed set of tunable property names is fixed in an XML configuration file that is packaged in the daffodil-lib artifact.
It should be possible to create a build task that re-writes the package.json file to include schema restrictions on the tunable property names that are derived from that upstream configuration file. Then the built extension could better validate launch.json files that use tunables.