Replace FTNetworkTracer with observer middleware #110
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.
Refactor network observation mechanism from a single tracer to a flexible observer protocol. This change replaces the concrete
FTNetworkTracerdependency with a newNetworkObserverprotocol, allowing for multiple custom observers. TheURLServernow supports an array of observers that receive lifecycle callbacks for each request.Key Features:
FTNetworkTracerdependency with a protocol-orientedNetworkObserver, enhancing flexibility and extensibility.URLServernow manages an array ofNetworkObserverinstances, enabling different modules to independently observe network events.NetworkObserverprotocol uses anassociatedtype Contextto pass correlation data (e.g., request ID, start time) betweenwillSendRequestand subsequent completion callbacks.NetworkObserverTestsand aMockNetworkObserverdemonstrate better test isolation and clarity.Package.swift: Removed the external dependency onFTNetworkTracer.Changes Summary:
FTNetworkTracer?[any NetworkObserver]FTNetworkTracerNetworkObserverprotocolrequestId,startTimeassociatedtype Contextmanaged by observerNetworkTracerIntegrationTests(deleted)NetworkObserverTests(new)