boundary

Hate to bring this up. But one more issue . Unable to send images when using the baml go client . 

The BAML Go code generator produces *types.Image for optional image parameters (image: image?), but the encoder is  causing a panic.

here is what is appearing to be happening

 1. BAML definition: image: image? generates Go signature: image *types.Image
  2. types.Image is defined as type Image baml.Image (interface)                                                           
  3. When passed to Kwargs: map[string]any{"image": image}, the encoder receives *types.Image                                                            
  4. In encode.go, the InternalBamlSerializer type assertion fails on *types.Image 
  5. Falls through to default case → "unsupported type" error  

Please let me know if you have a known work around that I could try. Thanks!

thats def a bug. temporary workaround use `image[]`

these are easy fixes and (hopefully) one time!

thanks! added a test as well!

https://github.com/BoundaryML/baml/pull/2996