Closed rsmithsa closed 1 month ago
Hi @rsmithsa
Thanks for the addition. However, state
is declared as an enumeration and shall be used like that.
Unfortunately, there is already an enumeration State
related to the status/progress of a tuned model.
The PR should take this into consideration. Thanks.
Cheers, JoKi
OK, it seems that Google has changed the response of tuned model not using state anymore but done
.
See here: https://ai.google.dev/api/tuning#response-body
Hi @rsmithsa I'm going through the $discovery response and update all types accordingly. It seems there have been quite some additional changes to the API. I'll fix this completely during the weekend with a new minor release coming out as a result.
Apologies, I didn't see you using enums elsewhere. The file response does still use an enum File & State.
This is a slightly different enum to the tuned model - so I added a new 'FileState' enum for this.
It might be worth refactoring the current 'State' enum to something like 'ModelState' but this would be a breaking change.
Hi @rsmithsa
Yes, exactly. The $discovery of the API has a few more changes. There's also a new Chunk
type which has another State
enumeration. I'm working through all this and next release shall have it.
Thanks for the initial pointer and bear a little with me.
Cheers, JoKi
Hi @rsmithsa
I integrated your suggestions into release 1.6.5 See here: https://github.com/mscraftsman/generative-ai/releases/tag/v1.6.5
Added the 'State' property to the file resource: [(https://ai.google.dev/api/files#File)] #33