-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Send 404 when the resource or author is not found #48
Comments
Oh, wow. This is a regression. What routes does this happen on? |
Reproduced on |
Oh! nvm, It is a bug! You were faster than me xP Thanks again. |
I found a discrepancy in the 404 errors: Shouldn't both responses be the same? |
Fair point, I'll address this as well tomorrow. Thank you |
…pull up resources by user/updates by resource; also check if listResources has any results and if the array is empty (i.e. no more results) then send a 4 04 instead of a plain empty array off to infinity; closes #48.
Took me one extra day - sorry. Had stuff going on yesterday. |
…pull up resources by user/updates by resource; also check if listResources has any results and if the array is empty (i.e. no more results) then send a 404 instead of a plain empty array off to infinity; closes #48.
Hello!
Right now when you search for a resource/author that doesn't exist you get an interesting response:
My suggestion is just adding a 404 error when this happens:
By doing this way, we (devs that use the API) can easily catch the error rather than checking if a value is null.
Also.... Thanks for this amazing tool.
The text was updated successfully, but these errors were encountered: