Hi,
as far as I can see target properties are not exported via the file API.
I was a bit surprised to see that. That would be an easy (I think) way to get information to IDEs. This could be command line arguments for a target when starting it, e.g. in a debugger, environment variables, and more like that.
There could even be a target property which lists the target properties which should be exported.
Does that sound useful, or are there reasons against this ?
Alex
A flat list of properties without any semantic meaning is not in the spirit of what the file-api currently produces. IMO it’s better to identify specific use cases and provide dedicated well-defined fields for them.
command line arguments for a target when starting it, e.g. in a debugger
We already have a debugger field holding a workingDirectory entry corresponding to the DEBUGGER_WORKING_DIRECTORY target property. That property was itself a generalization of the VS-specific VS_DEBUGGER_WORKING_DIRECTORY. One could extend that approach to generalize VS_DEBUGGER_COMMAND_ARGUMENTS too, and add another entry to the debugger object in the file-api.