Tool Response Discussion - Should tools be abstract?
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 115
Description
- [ ] Documentation on response parameters/Discussing parsing tool output and best ways to output it - do we want tools to just be a black box for the user?: https://github.com/Azure/azure-sdk-tools/pull/11432/files#r2270766511
- [ ] Also related to above, for parsing tool output: https://github.com/Azure/azure-sdk-tools/pull/11432/files#r2271140956
- [ ] Do we want to use DefaultCommandResponse? https://github.com/Azure/azure-sdk-tools/pull/11432/files#r2270758074
Contributor guide
Research direction
Start with the referenced discussion in Azure/azure-sdk-tools pull request 11432, especially the comments on response parameters, parsing tool output, and DefaultCommandResponse. Review the surrounding tool response implementation and documentation mentioned there. Done means the abstraction and response-format decisions are resolved and reflected in the relevant documentation or code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100