-
Notifications
You must be signed in to change notification settings - Fork 713
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
Ensure Consistent 400 Response for Invalid Input in Kolibri Public Content APIs with Studio #12807
Comments
can I take this issue? |
Hi @manzil-infinity180, Sure you can! I have assigned it to you. Thanks for contributing |
Feel free to ask any questions you have on the way @manzil-infinity180 :) |
Sir , I know that this issue has already been assign but can i work together to solve this problem ? |
Hello @rajRishi22 , I have already solved this issue I will raise pr in some following day. You can take a look at some other issues with no assignee |
Hello @manzil-infinity180 , I will look into other issues. |
can I take this issue? |
Hi @qmhqmhqmhqmh, thanks for volunteering! It's best to always preview whether an issue has an assignee or no. This one is already taken and even has a pull request linked. There are other contributing opportunities in several repositories. See the contributing guidelines including links to issues suitable for contribution for each repository here:
You can also see the list of unassigned "help wanted" or "good first issue" issues across all repositories. |
Description
Currently, the Kolibri public content APIs, specifically retrieve function of ContentNodeTreeViewset and ImportMetadataViewset handle invalid input by returning a 404 response. To ensure consistent API behavior across Kolibri and Studio, we need to update these views to handle invalid input in a way that aligns with the implementation in Studio.
Tasks:
Expected Outcome:
References:
We would want to refactor similar to this PR.
The text was updated successfully, but these errors were encountered: