Ivan Klass

But the main problem is that when you're writing your own app, it also adds content hash of your own package you can't opt-out, and it's a disaster for merging...

Also fighting with that issue A simplified example - [scastie url](https://scastie.scala-lang.org/JpKK7cUYS1iPv1Jlx3sgrA) ```scala //> using dep io.getquill::quill-jdbc-zio:4.8.6 import com.zaxxer.hikari.HikariConfig import com.zaxxer.hikari.HikariDataSource import io.getquill.* import io.getquill.jdbczio.Quill import io.getquill.context.* import zio.* import java.util.Properties...

@raquo thanks. Just as an idea, maybe add something like ```scala // explicitly move child from current owner to another parent ChildCommand.TransferToNewParent(elementExpectedToBecurrentChild, newParent, position = ???) // or // explicitly...

Shouldn't this be closed in favour of [sentry-opentelemetry-agent](https://docs.sentry.io/platforms/java/tracing/instrumentation/opentelemetry/#using-sentry-opentelemetry-agent-with-auto-initialization)?

I would also love this feature to exist. Currently what I've done locally is ```scala extension [T](signal: Signal[T]) inline def toStream: EventStream[T] = new StreamFromSignal(parent = signal, changesOnly = false)...

I end up with combining both options and value in a single case-class like below ```scala case class SelectOptions[+T](options: Vector[T], tryChoose: Option[T]): private val withIndex = options.zipWithIndex val chosen: Option[T]...

While adapting "classic" cron string to cron4s format may not seem very tricky with the code like below ```scala def parseMinuteBased(e: String, implySeconds: String = "0"): Either[Error, CronExpr] = parse(s"$implySeconds...

The workaround (I wish I've avoided): ```sbt myApiCrossPlatformProject .settings( description := "Contract definitions for API between server and client" ) .jvmSettings( // https://github.com/softwaremill/tapir/issues/4935 libraryDependencies += Dependencies.tapirServer ) ``` in .jvm/src/...

@adamw I understand about runtime changes. Maybe it's possible to add an extra EndpointInput type, like PathSegment? That will only capture parts without "/", so it would be backward-compatible

> The change that we might introduce in Tapir, is to move the `.onDecodeFailureNextEndpoint` attribute to `core` (or rather, deprecate the old one, and add a new one). But as...