microsoft / microsoft/debug-adapter-protocol
ChecksumAlgorithm should include SHA384 and SHA512
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 173
- Avg merge
- 7d 7h
- Merged PRs (30d)
- 2
Description
cl.exe for example supports these as a checksum algorithm: https://learn.microsoft.com/en-us/cpp/build/reference/compiler-options-listed-alphabetically?view=msvc-170, so it would be useful to have these defined in protocol so that these checksums can be easily reported across DAP.
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 locating the ChecksumAlgorithm definition in the debug adapter protocol and review how existing checksum values are declared and documented. Add SHA384 and SHA512 alongside the current algorithms, then verify that the protocol can report both values consistently across DAP.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100