-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[API] Fix 9544 | return 200 when reaction already exist #9550
[API] Fix 9544 | return 200 when reaction already exist #9550
Conversation
3d88f40
to
67767b4
Compare
Co-Authored-By: zeripath <art27@cantab.net>
Is StatusOK really right here ? - I would have thought StatusConflict would have been better? However, I think there's a place for putting a 200 here. |
We can still decide wich status we return - github does it the 200 way reverence: link But this is also a smal code/refactor <- now we can explicit handle dubble add and filter/find reactions by more options |
Codecov Report
@@ Coverage Diff @@
## master #9550 +/- ##
==========================================
- Coverage 41.99% 41.98% -0.02%
==========================================
Files 577 577
Lines 75939 75970 +31
==========================================
+ Hits 31890 31894 +4
- Misses 40100 40132 +32
+ Partials 3949 3944 -5
Continue to review full report at Codecov.
|
@lafriks done |
@techknowlogick ready for merge 🚀 |
* add ErrReactionAlreadyExist * extend FindReactionsOptions * createReaction check if exit before create
@techknowlogick since reaction api is not in 1.10.0 I only backported error handling |
fix #9544