Repository navigation
Conversation
Refactor createNotificationException to always return UnknownNotificationException. Signed-off-by: S.J. Guillot <58807831+sjg2203@users.noreply.github.com>
|
This was fixed by #1134 already. |
Right (completely forgot about it!), #1134 hasn't gone into production yet (not part of v10.4.0), right? If it did, it seems that it didn't fix the issue. |
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
Refactor createNotificationException to always return UnknownNotificationException, resolving repeated log warnings about deprecated InvalidArgumentException.
🤖 AI (if applicable)