upgrade the version of typespec #2286
Conversation
kazrael2119
requested review from
sarangan12,
joheredi,
qiaozha and
MaryGao
as code owners
.../typespec-test/test/openai_generic/generated/typespec-ts/src/api/audio/translations/index.ts
Show resolved
Hide resolved
packages/typespec-test/test/openai_modular/generated/typespec-ts/review/openai_modular.api.md
Show resolved
Hide resolved
| | Uint8Array | ||
| | ReadableStream<Uint8Array> | ||
| | NodeJS.ReadableStream; | ||
| file: string; |
There was a problem hiding this comment.
Could you help to explain why we change this?
There was a problem hiding this comment.
For RLC layer, we only generate
string
| Uint8Array
| ReadableStream<Uint8Array>
| NodeJS.ReadableStream;
for binary bytes, if it's other encoded bytes, we will just treat it as normal string, because of the tcgc lint rule for bytes in multipart/form-data request, we have to remove the encode decorator.
There was a problem hiding this comment.
Maybe the right solution for RLC here is to figure out a way to suppress the linter rule in TCGC, instead of changing the typespec ?
There was a problem hiding this comment.
This will come back to be a File with Mary's PR, is that correct?
There was a problem hiding this comment.
yes, @MaryGao can you help verify if your calculation will not rely on any encode information on bytes?
There was a problem hiding this comment.
update the typespec compiler version to 0.53