-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[stable28] fix: avoid douple expireDate
parsing
#44912
Conversation
d7c9de2
to
3cd5a7f
Compare
3cd5a7f
to
4292ff6
Compare
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.
This actually breaks Talk attachment:
https://github.com/nextcloud/spreed/actions/runs/8736657894/job/23972035833?pr=12147
396244f
to
fc18a09
Compare
/backport to stable27 |
It will only backport after the PR was merged, which will not be during the current RC freeze |
1539611
to
1cf2bed
Compare
@nickvergessen what's the status, is this good for you? |
@nickvergessen That has been handled here : #45604 |
1cf2bed
to
9237d4c
Compare
… logger Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
`expireDate` can be set once and used anywhere needed, the current implementation, duplicates this behavior which leads to `parseDate` receiving an a date object it parsed and returend earlier in the createShare method. Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
9237d4c
to
e8b7a4b
Compare
[EA] New value type (\DateTime) is not matching the resolved parameter type and might introduce types-related false-positives. Signed-off-by: Joas Schilling <coding@schilljs.com> Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
e8b7a4b
to
4d748b9
Compare
Backport of #44838
Warning, This backport's changes differ from the original and might be incomplete⚠️
Todo
Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.