feat!: Remove interior mutability of HealthCheckRegistry
#258
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.
Switch to using
OnceLock
to allow setting the health checks on theAppContext
after it is created. The method to set the health checks is private to the crate, so we have control over when the checks are set on the context.This has some impacts on public-facing APIs:
App::health_checks
takes a&mut HealthCheckRegistry
instead of a non-mutable refAppContext::health_checks
returns the list of health checks. (Alternatively, we could have returned an Option)HealthCheckRegistry::new
method non-public. This aligns with theServiceRegistry::new
visibility.Closes #257