Fabian Holler

The bug is back. For an postgresql `TEXT[]` column xo generates a struct field with the wrong type `[]sql.NullString`. @kenshaw could you reopen the ticket or should I create a...

@kenshaw thanks a lot

@hhhapz yes, it does. The generated code: ```go // Testtable represents a row from 'public.testtable'. type Testtable struct { Textarray []sql.NullString `json:"textarray"` // textarray } ```

@hhhapz ups, sorry, I copy & pasted accidentally the previous version :-) With your branch it is: ```go // Testtable represents a row from 'public.testtable'. type Testtable struct { Textarray...

We also require support for B3 propagation especially on the GRPC server-side. We have GRPC-Clients in different languages (e.g. python, php, nodejs) which propagate the tracing information in B3 format...

We also encountered the issue that staticcheck does not complain if a deprecated struct field is assigned when the struct is instantiated (in another package). This causes that from now...

@l3pp4rd depends on the effort :-). I ended up writing my own simple mock instead, that works okayish for my current usecase. Do you maybe have an idea what the...

The issue has been introduced by the change: https://github.com/compose-spec/compose-go/pull/546 It can be reproduced with [this compose.yaml file](https://gist.githubusercontent.com/fho/3a961e31ad7179f7955107ac8fbb2af6/raw/5332b1803ab634d246b44b48b0b58a83ac06a3d3/compose.yaml). Running `docker compose config` on my machine takes with - **Docker Compose version...

@mroethke is this still wip or should we close the PR?

@cfoote do you maybe have time to resolve the merge conflicts. It would be awesome if we could get this feature in.