Moritz Lang
Moritz Lang
> I'd like to find a way to avoid that if we can. > @Lukasa We briefly chatted about the reasoning of having it API breaking here: slashmo/gsoc-swift-baggage-context#8
This PR is now superseded by https://github.com/apple/swift-log/pull/235
For the time being, I'd like `swift-otel` to specifically target Server-Side Swift. The official [opentelemetry-swift](https://github.com/open-telemetry/opentelemetry-swift) client is more geared towards running on iOS, so I'd recommend to use it instead...
@ktoso Funny how we ended up with almost this design, not passing `Baggage` to the `MetadataProvider` directly 😊
@FranzBusch Agreed that this is not desired anymore 👍
@FranzBusch Yep, let's close it. The approach you describe sounds good to me 👍
@wibed Thanks for the bump 🙏 Do you have a particular use case in mind for having the concept of resources in the library?
Superseded by #76.
Thanks for bringing this up! Quoting the OTel spec: > This method provides a way for provider to immediately export all spans that have not yet been exported for all...
@0xTim Glad to see this being tracked now 👍 Feel free to ping me once you're starting the implementation, then I could update my HTTP client/server example to use Vapor...