Collector 0.2.0 #1
Open
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.
Collector 0.2.0
♻️ Current situation
There is no way to only collect metrics or traces. You always get both features at once without the choice of one.
Dependencies should only be part of a framework, if they are essential to them - which is not the case for NIO in MetricCollector.
There is no way of injecting/extracting context from a Foundation URLRequest.
💡 Proposed solution
Separate Collector into MetricCollector and TraceCollector with only relevant dependencies between the two. Collector is still a package that can be imported (essentially MetricCollector + TraceCollector).
Remove direct dependency on NIO for MetricCollector. We still have it in the list through SwiftPrometheus though.
Add Context Propagation for URLRequest right in the main repository.
Implications
Minor interface changes from NIO to async/await.
Testing
There are no tests so far.
Reviewer Nudging
The changes are actually quite minor, so you should be able to skim over all of them.