ollls / zio-tls-http Goto Github PK

with this case case GET -> Root / "user" :? uid(parm) =>
where uid is defined as object uid extends QueryParam("uid")
I expect request like /user?uid=1234 would match the case, but it finally return a 404
it's zio-tls-http 1.1.0-m1 I've used

Hello zio-tls-http maintainers!

Thank you for your work so far!

We are currently investigating using your library to establish TCP/TLS connections from a ZIO application (so without the HTTP layer), but when we included your library as a dependency, our logging setup exploded. A bit of snooping around uncovered that the logback-test.xml you keep in your main/resources folder is to blame: it ends up on the classpath (because it's in main/resources) and due to logbacks precedence rules, it takes precedence over any defined logback.xml in the main project, effectively negating it.

Can this file be moved to the test folder instead? I imagine the Readme also needs a bit of an update then.

Kind regards,
Nathan

ZIO 2.0 is at Milestone 4, with an RC expected in the next few weeks.
https://github.com/zio/zio/releases/tag/v2.0.0-M4

The API is nearly stable at this point, so any early migration work against this version should pay off towards the official 2.0 release.

The progress is being tracked here:
zio/zio#5470

The Stream Encoding work in progress is the only area where the API might still change before the RC.

We are actively working on a ScalaFix rule that will cover the bulk of the simple API changes:
https://github.com/zio/zio/blob/series/2.x/scalafix/rules/src/main/scala/fix/Zio2Upgrade.scala
We highly recommend starting with that, and then working through any remaining compilation errors :)

To assist with the rest of the migration, we have created this guide:
https://zio.dev/howto/migrate/zio-2.x-migration-guide/

If you would like assistance with the migration from myself or other ZIO contributors, please let us know!