feat: indicate reason for preloading notifications#54377
Merged
Conversation
miaulalala
approved these changes
Aug 12, 2025
ChristophWurst
approved these changes
Aug 18, 2025
st3iny
force-pushed
the
feat/notification-preload-reason
branch
from
e31ecc3 to
44131de
Compare
Signed-off-by: Richard Steinmetz <richard@steinmetz.cloud>
st3iny
force-pushed
the
feat/notification-preload-reason
branch
from
44131de to
f95ce30
Compare
st3iny
added
4. to release
github-project-automation
bot
moved this from 🏗️ In progress
to ☑️ Done
in 💌 📅 👥 Groupware team
ChristophWurst
added
the
pending documentation
Member
|
New API -> docs |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #54231
As suggested by Joas in nextcloud/notifications#2452 (comment).
This makes it easier for implementations/apps to decide on what data to preload.
Checklist