microsoftgraph / microsoftgraph/msgraph-sdk-powershell
Suggested Improvement: Enhanced Error Messaging
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 898
- Forks
- 230
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 31
Description
Feature: Fluent API
I appreciate the addition of fluent APIs in the PowerShell SDK v2 preview. Fluent APIs provide design-time feedback for calling Microsoft Graph and allow me to catch errors earlier in the development process. This improvement has streamlined my workflow and reduced the time spent on debugging.
Suggested Improvement: Enhanced Error Messaging
While fluent APIs help catch errors early, I believe that providing more detailed error messages would further improve the developer experience. When an error occurs, it would be helpful to receive not only the error code but also suggestions for possible resolutions or links to relevant documentation.
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 the Microsoft Graph PowerShell SDK v2 fluent API error-handling entry points; the issue does not name a file, test, or command. Define completion as errors including the error code, possible resolution suggestions, and links to relevant documentation, then add coverage for the resulting messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100