David Hoepelman

As a first step, I have [a version allowing `@Builder.Constructor` on the record level](https://github.com/immutables/immutables/compare/master...dhoepelman:builder_constructor_records?expand=1), I will try to open a PR soon. Question to the maintainers, currently all record-level annotations...

If you want this behavior, you can define your own `implicit val stringLong: Writes[Long] = l => JsString(l.toString)` in scope.

1 and 3 are natively possible in play-json versions (`Json.using[Json.WithDefaultValues].format` and `JsonConfiguration(SnakeCase)` respectively) The main advantage for me is that this lib turnings thrown exceptions into deserialization errors

Hi @abhsrivastava play-json supports only lowerCamelCase by default. This lib follows that behavior ``` scala> case class Foo(accountNumber: String) defined class Foo scala> implicit val format = play.api.libs.json.Json.format[Foo] format: play.api.libs.json.OFormat[Foo]...

Still present in 2.14.0. Is independent of `@Inject`, probably any annotation causes this. Encountered this with Jackson `@JsonCreator`: ``` record Wrapper(@JsonValue String json) { @JsonCreator(mode = JsonCreator.Mode.DELEGATING) public Wrapper {}...

This is already possible by using `table.insertOrUpdate(yourObject)` For slick-pg, you will need to add the following to your postgres driver top level: // Add `capabilities.insertOrUpdate` to enable native `upsert` support;...

Interesting, I will check out your changes to see if there is anything worthwhile > all checks are now failing fast This is a non-going. If you want fail-fast you...

I also support structured logging. A major difference with MDC (like `withLoggingContext(Async)`) is that it can be any complex object instead of only key with string values. A nice implementation...

Workaround provided by lukaseder [in this SA post](https://stackoverflow.com/a/76445346/572635) to use plain SQL templating ```java Field jsonbConcat(Field f1, Field f2) { DSL.field("({0} || {1})", f1.getDataType(), f1, f2); } ```

This would be good to have support for. It's probably relatively easy to do, I think some thing(s) are not marked as covariant when they should be. An existing workaround...