Andy Day

This should resolve #2159. I'm hesitant to do this for a `JSON` field which is an Array type, but in theory those should also be nillable?

This change adds an example of how to test a middleware function.

Add option to allow for a generated code comment

3

We'd like for GH / Reviewable to understand these files are generated. Would you be open to adding a flag like: `--ts_proto_opt=header=true` Which would prepend something like `// Code generated...

#### Type of PR: - [ ] Bugfix - [ ] Feature - [ ] Code style update - [ ] Refactor - [x] Build-related changes - [ ] Documentation...

Add withRecursive method

3

#### Type of PR: - [ ] Bugfix - [x] Feature - [ ] Refactor - [ ] Code style update - [ ] Build-related changes - [ ] Test...

No SetNillable setter is generated for array Bytes field

4

If you use `field.Bytes` with an array Go type (e.g. `type ByteArray [12]byte`) and set that field as optional & nillable, you would expect there to be a `SetNillable` setter...

Use go:embed for pretrained gpt2 tokenizer, add missing json

1

This change adds the missing json file to the repo, as well as embeds both the vocab and merge files and uses the embedded FS to create the pre-trained tokenizer.

Ran `gofmt -s -w`.

https://platform.openai.com/docs/api-reference/chat/create#chat/create-stream Will likely look very similar to [this](https://github.com/fabiustech/openai/blob/e382c1a504caa8283e9784d26b75c46261000a0e/completions.go#L141-L196).