Closed MichaelMcCulloch closed 6 months ago
Hi @MichaelMcCulloch
Thank you for the PR, The challenge here is maintaining compatibility with various providers. I'd rather stick with one provider - that is OpenAI - adding more creates maintenance challenges.
I see what you are saying. But does making a particular field optional add maintenance challenges? How would you request that I improve the current pr?
I see the entire types module has been refactored. So that answers my question. Would it be acceptable if I modified my pr to match?
Hey I had added scope tag and I missed to respond about your comments, sorry about that.
I see your point, however timeline-wise after your PR I had added section about this topic of what should be within the scope of this library https://github.com/64bit/async-openai?tab=readme-ov-file#contributing - so please know that your PR's contribution came in the form of documentation
As you can see from the log, the
created
timestamp is not always present, andobject
never is. Now it's compatible with both.