Octocrab and 204 responses #506
Replies: 5 comments 5 replies
-
I started tracking all of these here: https://github.com/users/manchicken/projects/4/views/1 I did a quick write-up of my process here: https://dev.to/manchicken/tackling-a-large-volume-of-simple-problems-in-an-open-source-project-5fn3 |
Beta Was this translation helpful? Give feedback.
-
I've gone through a bunch of the API endpoints with 204s, and the good news is that so far I haven't found any more that are broken. The bad news is that there are ~164 left to sift through. The biggest thing I'm finding is that there are a lot of gaps in API coverage. @XAMPPRocky, do you have any thoughts or documentation regarding your philosophy on which API endpoints get a semantic function and which ones don't? If—after I finish this little 204 audit—I wanted to add some, is there any guidance on which ones would be wanted and which wouldn't? Many thanks for the opportunity to help. |
Beta Was this translation helpful? Give feedback.
-
@dmgorsky, I see a bunch of the issues you made to add semantic API functions for uncovered endpoints. I'm working on adding tests for these 204 cases (and fixes where needed). Would you like to collaborate on putting prioritizing the endpoints that need to be added? If our maintainer says all endpoints get a semantic function then this could be a fun series of little projects. |
Beta Was this translation helpful? Give feedback.
-
With that last PR, I’ve covered all of the 204 cases for which semantic functions exist. 🥳 |
Beta Was this translation helpful? Give feedback.
-
@dmgorsky I finished the project I was working on. Do you have a process you were following for adding functionality? I'm gonna see if I can find an endpoint among the ones you identified as missing to implement. If you—or anybody else—has a prioritized list, I'd be open to addressing these in an order. |
Beta Was this translation helpful? Give feedback.
-
There are a number of endpoints which return a 204, and it kinda looks like a bunch of them are currently broken. The one test I added in #503 as part of issue #504 shows how the standard
FromResponse::from_response()
approach doesn't account for this.There appear to be 263 endpoints which could return a 204, so while I am tempted to just fix the ones I'm trying to use, it kinda seems like we need a more comprehensive approach.
Here are the endpoints I found a 204 on, per GitHub's OpenAPI spec: findings.csv
Beta Was this translation helpful? Give feedback.
All reactions