-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[10.2.0] Treat send attempt as unsuccessful when there is a message. #35221
Conversation
3e5bedb
to
eea9382
Compare
Codecov Report
@@ Coverage Diff @@
## release-10.2.0 #35221 +/- ##
====================================================
- Coverage 64.39% 64.39% -0.01%
Complexity 20049 20049
====================================================
Files 1285 1285
Lines 76842 76844 +2
Branches 1308 1308
====================================================
Hits 49480 49480
- Misses 26978 26980 +2
Partials 384 384
Continue to review full report at Codecov.
|
@VicDeo Please do not merge until the decisions about the release are made. |
eea9382
to
b54f30c
Compare
I have tested this and it works fine on the frontend. Is this the expected behavior? |
@paurakhsharma |
I double checked and this is the network response in 10.1 |
@VicDeo would be good to also update the frontend unit tests. I believe we have some for the email part. |
backend unit tests as well... but here I believe this is not coverable... please always add statements and reasons if you decide to skip unit tests |
@VicDeo so this changes the response format ? I thought this PR was an attempt to bring it back to what it was before |
@PVince81 to bring it back I need to kill the controller and send the response from not coverable as I can't mock |
10.1 sends a response with #33180 changes it send a response from that's why the responses differ - one is pure AJAX and other is OCS |
@VicDeo would you qualify this as API change ? or would the new format be solidified as a public API if it's OCS ? |
the old API as far as I remember was not OCS so considered private |
@michaelstingl I also assume no client was using this private API in ajax/share.php |
Is this the mail for public links? Never made it to the clients because of the missing proper API. |
@PVince81 it didn't look like a public API at all as it needed logged in user and a valid CSRF token: |
|
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.
👍
Backport of #35220
Description
result.ocs.meta.status
is 200 when the email was not sent.Related Issue
Motivation and Context
Frontend says that email is successfully sent even when it has been not sent.
How Has This Been Tested?
See #35218
Types of changes
Checklist: