be44a22903
Initially I considered using #i, #s, etc. to coerce to specific types, but then it wasn't clear of the semantics (particularly for bool, where JSON bool true/false, Python bool True/False). But it turns out that we can just coerce any key from a JSON string. Users can _probably_ type JSON strings for most things, or use variables to run scripts to generate them, this allows essentially complete flexibility to define the data types needed to populate the launch spec. The purpose of this is to allow some level of automated setup by requesting data from the user and then (subsequently) saving the flattneed config to the vimspector config file. |
||
|---|---|---|
| .. | ||
| vendor | ||
| __init__.py | ||
| breakpoints.py | ||
| code.py | ||
| debug_adapter_connection.py | ||
| debug_session.py | ||
| developer.py | ||
| gadgets.py | ||
| install.py | ||
| installer.py | ||
| output.py | ||
| settings.py | ||
| stack_trace.py | ||
| utils.py | ||
| variables.py | ||