The latest updates on your projects. Learn more about Vercel for Git ↗︎

Actually, lets include both streamOptions: { includeUsage: boolean } (prefer camel case for our API) and streamUsage: boolean. OAI might add more fields to their stream_options API in the future, in which case we'd like a way to support those too!

@bracesproul, I think I've made the changes you are after.

Getting a few 400s when running integration tests:

400 The 'stream_options' parameter is only allowed when 'stream' is enabled.

Seems like we may need to be a bit more selective on how we populate this?

Is it possible to run the integration tests outside of being kicked off by a maintainer?

To address the 400 for stream: false when requesting usage data I've updated so that either stream_options: {include_usage:true}/ streamUsage true will force the stream flag to be set to true, and if not fallback to this.streaming. To make it BC I've altered streamUsage to default to false.

It may make more sense to just throw the error back the user of the library, stating that you can't request stream usage info with the stream flag set to false?

Let me know if there's any other changes you'd like to see before its ready to merge

Thanks

Changed to default to true, avoid passing as an invocation param if this.streaming is false.

Thank you!