OwningComponentBase implements IAsyncDisposable #62583
Merged
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.
OwningComponentBase implements IAsyncDisposable
Description
This pull request enhances the
OwningComponentBase
class by adding support for asynchronous disposal, improving resource management, and updating tests to validate the new functionality. The most important changes include implementing theIAsyncDisposable
interface, adding new methods for asynchronous disposal, updating the public API, and introducing new test cases to ensure proper behavior.Enhancements to
OwningComponentBase
:src/Components/Components/src/OwningComponentBase.cs
: Updated theOwningComponentBase
class to implement theIAsyncDisposable
interface. AddedDisposeAsync
,DisposeAsyncCore
, and updated theDispose
method to handle both synchronous and asynchronous disposal of the service scope.Public API updates:
src/Components/Components/src/PublicAPI.Unshipped.txt
: AddedDisposeAsync
andDisposeAsyncCore
methods to the public API to reflect the new asynchronous disposal capabilities.Testing improvements:
src/Components/Components/test/OwningComponentBaseTest.cs
: Added new test cases to verify the behavior ofDisposeAsync
, ensure that accessing scoped services after disposal throws an exception.Fixes #25873