Remove unnecesarry properties when parsing any results from a GitHub API request
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 143
Description
Right now, when we make an HTTP request to the GitHub API, we are parsing all of the properties from the response, even the ones that we are not using.
Sometimes, some properties will have unexpected values (like `null` values), in which case the flow will fail.
We should only parse for the properties we actually need.
For this issue, we have to look at all the places we are making those calls and then change the parse step accordingly.
Contributor guide
Research direction
Start by locating every HTTP call to the GitHub API and its response-parsing step across the repository. For each call, identify which response properties the surrounding code actually uses and verify how unexpected null values currently fail. The work is done when unused properties are no longer parsed and all affected flows still handle the needed values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github
- Domain
- api, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100