Generic Attachment-Processing registration - #453
Draft
ktsorensenWX wants to merge 7 commits into
Draft
Conversation
restjohn
marked this pull request as draft
July 23, 2026 16:28
Contributor
Author
|
Also contains - feat(service): run pending attachments through registered hooks |
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
1 participant
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.
Lets a plugin's init() contribute attachment-processing hooks that core collects and holds in memory, following the existing WebRoutesHooks pattern rather than the icons/feeds DB-repository pattern (hook functions are live code, not persistable data). No hooks are registered yet and nothing consumes them — this is groundwork for an upcoming ClamAV plugin.
Work in progress