Connor Tumbleson
Connor Tumbleson
You'll find the problem with just adding null checks is the types don't suggest they are null, so it becomes a bit more of a fix to make things nullable...
I'm torn between nullable or `-1` at this point. Nullable because its semantically better, but that causes all downstream users to type for something nullable that generally won't be for...
I have been debating this exact problem and haven't really come up with a good solution, but I do like the different response class. My grip is kinda with Google....
I'm torn because you cause everything downstream to require handling nulls, so that's my hesitancy. These are fields that been there for many years at this point - I'm more...
I missed that this was the streaming payload on first peek. Do you have name of the non-OpenAI provider and the API call you are making? I presume this is...
cc @bytestream who has some ideas on Exception improvement. As I look at this - I'm wondering if we ever get a 200 back from OpenAI that is not valid...
> I personally thought the clue was in the name `openai-php/client` and it was exclusive to OpenAI 😅 Like would be easier if that was the case for sure lol....
Thanks! I've got my head down trying to finish this Responses API, but will visit this for sure soon
I remember digging into this a year ago and there was no good way to make it more sane without a ton of breaking changes. - As you noticed once...
@REAndroid > Begin dex protection :o