-
Notifications
You must be signed in to change notification settings - Fork 10
changed endpoint for getting al hightlights. Status code is now 200 w… #248
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
Conversation
Hey @niraymak are there other endpoints from other controllers that will also need changing? I wonder if this is the only endpoint with this issue. |
Following endpoint should be changed:
Shall I change them and push them to this PR? |
Changed the endpoints and pushed them to the PR |
Awesome, thanks @niraymak. Please also change the postman tests ^^' |
@Brend-Smits test results are 100%. The corresponding tests already check for status code 200. I am not sure what to update in the Postman tests. Can you tell me what tests I should add? |
Ah right, we don't have any tests for checking status codes when there are no entries. That's fine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove try-catch as discussed in Teams and we're good to go.
Since #240 is now merged, make sure the documentation is updated! |
…hen the list is emtpy.
Description
A few sentences describing the overall goals of the pull request's commits.
Type of change
Checklist
Steps to Test or Reproduce
Link to issue
Closes: #207