Strange handling of empty json array (possibly zio-schema bug?)

[russwyte]

Describe the bug
Routes that produce JSON don't correctly handle empty collections. The resulting JSON should always have a field with an empty JSON array - but instead the field is omitted altogether.
To Reproduce
See this gist
result of run is:

unexpected: {"bars":[1,2,3]}
expected: {"bars":[1,2,3]}
unexpected: {}
expected: {"bars":[]}

Additional context
This causes breakage in codecs when lists are not optional and are empty

The gist also shows a work-around that might shed light on a possible fix?

[russwyte]

This is the issue. It seems like the default should be false - as empty collections are valid data.

[russwyte]

Adding this works - but this seems like it should be the default as it is in zio-json and elsewhere

  val routes = Routes(
    unexpected.implement(foo => ZIO.succeed(foo)),
    expected.implement(foo => ZIO.succeed(foo))
  ) @@ CodecConfig.withConfig(CodecConfig(ignoreEmptyCollections = false))

[jdegoes]

@987Nabil Should we change the default here? I too would expect empty collections to be represented in responses (but missing collections to be accepted in requests -- notice the duality).

[987Nabil]

Yeah. I think we should