-
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
Fix the category update operation #356
Conversation
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.
The PR name is also not descriptive. One suggestion would be "Add category availability into category model"
But actually we do not just add the availability into model, we also fix the update operation by fixing the query for request and the result handler. |
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.
Missing updating the mock class and tests since you're changing the interface
For example, at tests/_support/MockCategory.php
Due to the fact that I also add the operation/CategoryUpdate, I think that I should add test for it too ? |
Yep, please add a test |
4746b84
to
b97461f
Compare
Because the category_string is required in category tagging to be able to work in ev1 event
b97461f
to
9a479e7
Compare
f373078
to
1433269
Compare
1433269
to
52a3823
Compare
Currently in local we use debian distro and the github runner use ubuntu so the curl error for connection refuse is difference so I have change the assert for connection refuse test. Maybe problem is curl version difference
52a3823
to
0addabc
Compare
The category update operation does not work at the moment due to using wrong query and the result handler parse the response in a wrong way
Checklist: