pjfanning opened a new issue, #304: URL: https://github.com/apache/incubator-pekko-http/issues/304
For some reason, Scala 2 does not seem to allow public access to package private constructors but Scala 3 enforces it. We also had to relax the scope on 2 constructors to allow pekko-connectors to compile with Scala 3. https://github.com/apache/incubator-pekko-http/pull/178 It turns out that Tapir also uses these exact same constructors but Tapir is in its own package. Tapir recently added Pekko HTTP support but didn't add Scala 3 support for Pekko HTTP (https://github.com/softwaremill/tapir/issues/3114). Should we start making these constructors (see https://github.com/apache/incubator-pekko-http/pull/178) public? If so, should we backport to 1.0.1 even though this will probably affect binary compatibility? Adding a hacky org.apache.pekko scoped util class to Tapir should allow a workaround that can create Content-Length/Content-Type instances. wdyt? @jrudolph @mdedetrich -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
