Repository navigation
Conversation
Assisted-by: ClaudeCode:claude-opus-5-5 Signed-off-by: Simon Kern <14980558+skjerns@users.noreply.github.com>
Assisted-by: ClaudeCode:claude-opus-5-5 Signed-off-by: Simon Kern <14980558+skjerns@users.noreply.github.com>
Include creators who no longer have access to the board, and skip removed users. Assisted-by: ClaudeCode:claude-opus-5-5 Signed-off-by: Simon Kern <14980558+skjerns@users.noreply.github.com>
…lter Assisted-by: ClaudeCode:claude-opus-5-5 Signed-off-by: Simon Kern <14980558+skjerns@users.noreply.github.com>
… into feat/2466-filter-by-creator
|
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.) |
Summary
I've recently had the necessity to filter cards created by myself. This PR introduces this functionality and is relatively non-invasively, mainly copying what other filters do.
The major design decisions were to introduce a new js function that filters a card by creator. This was necessary to be able to unit-test that function. This seemed like the only way to unittest without having the full suite setup. Let me know if this is not sufficient.
TODO
Checklist
🤖 AI (if applicable)
The code was created together with Claude Opus 5.5, reviewed by me, testing was done with a local instance manually (works in all views), PR was written by myself