microsoft / microsoft/debug-adapter-protocol
"readOnlyTarget" capability
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 173
- Avg merge
- 7d 7h
- Merged PRs (30d)
- 2
Description
Nuclide has a "readOnlyTarget" capability flag which disables some unsupported features of the debugger, for debugging static dumps. This should exist in the debug protocol too.
Instead of a master flag like "readOnlyTarget", we would prefer more specific flags for individual features. But capabilities usually enable features, not disable them, and it seems weird to have a flag like supportsStepping which must be set 99% of the time.
@mostafaeweda
@ebluestein
Which features are disabled by this flag? Do you think there would be different features supported in different situations (so they'd need to be disabled on a more granular level)?
VS docs: https://msdn.microsoft.com/en-us/library/d5zhxt22.aspx
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Nuclide's readOnlyTarget behavior and the linked VS documentation to identify which debugger features it affects. Check the existing debug protocol capability definitions, then document the agreed capability design and update the protocol specification once the scope is decided.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100