Repository navigation
fix(notifications): Use the target id in guest conversion notifications - #1669
Conversation
The rich object describing the converted-to account fell back to the guest id when the target account could not be resolved, so a failed conversion reported the guest twice instead of naming the account it was supposed to become. Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
a5ea525 to
00b52d8
Compare
|
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.) |
The rich object describing the converted-to account fell back to the guest id when the target account could not be resolved, so a failed conversion reported the guest twice instead of naming the account it was supposed to become.