-
Notifications
You must be signed in to change notification settings - Fork 342
Update @typespec/http-client-csharp to 1.0.0-alpha.20251009.7 #742
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update @typespec/http-client-csharp to 1.0.0-alpha.20251009.7 #742
Conversation
- Updated @typespec/http-client-csharp from 1.0.0-alpha.20251003.1 to 1.0.0-alpha.20251003.2 - Updated Microsoft.TypeSpec.Generator.ClientModel from 1.0.0-alpha.20251003.1 to 1.0.0-alpha.20251003.2 - Regenerated OpenAI SDK code with new generator version - Updated centrally managed package-lock.json file with new dependency versions
d31cf92 to
6b467cd
Compare
| public DateTimeOffset ExpiresAt { get; } | ||
|
|
||
| public string Object { get; } | ||
| internal InternalUploadObject? Object { get; } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we will need to customize this back to string
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The type is internal, is this just to maintain the previous behavior?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm maybe not necessary, but I noticed the serialization code changed as a result.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have yet to run the live tests, but I will try to validate this doesn't break anything if we change this to an enum.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JoshLove-msft - I ran the live tests and everything seems to be passing. Looking at the serialization code, it seems like it is functionally the same unless I'm missing something here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I missed that this was internal and the deserialization changes look to be functionally equivalent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a unit test that tests the round trip serialization of one of these models for sanity.
…ypespec/update-http-client-csharp-1.0.0-alpha.20251003.2
Updates the generator version to
1.0.0-alpha.20251009.7.fixes: microsoft/typespec#8710