Move calendar resource/room backend registration to IBootstrap #31007
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.
Fixes #29563
Old registration
^ only possible during
boot
, which imposes a potential loading order problem. Moreover both managers have to be instantiated and therefore cause a performance overhead for requests that don't need the backends.New registration
^ happens during
register
. No performance overhead, it's two string appended to arrays.I've tested it with the modified
calendar_resource_management
. The backends are still loaded and processed during the background job.Ref nextcloud/calendar_resource_management#45