fix(subscriber): panic when reloading Filtered #3328
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.
Motivation
Resolve #1629 without introducing a breaking change.
A workaround for this issue was introduced via
filter_mut
, which allows reloading theFilter
of aFiltered
layer — but it still doesn't support replacing the entireFiltered
layer.A breaking change was also proposed, but it comes with some downsides:
Alternatives
section here, it could introduce unintended side effects.Solution
This change adds support for reloading filtered layers without breaking the existing API by introducing a dedicated
Handle::reload_filtered
method for reloadingFiltered
layers, and aLayer::on_reload_layer
method for performing late initialization when aLayer
is reloaded.Handle::reload_filtered
invokes the newLayer::on_reload_layer
method on the layer. This method is responsible for registering the filter with the subscriber viaregister_filter_immut
.Unlike
register_filter
, theregister_filter_immut
function takes a shared reference to the subscriber, allowing filter registration after the subscriber has been fully initialized.Usage examples for are included in the inline documentation.
Fixes: #1629