Jose Alvarez
Jose Alvarez
We are assuming that native coins have `18` decimals (which might not be the case in the future)
## Context In order to deploy safes in chains where the addresses are not the ones we get using the usual deterministic deployment, we need to manually input the `factory`...
- Adding `custom-types` and ` custom-types-subpackage` for the java emitter config to account for custom code for OpenAI functions feature
**IMPORTANT:** Please for you review, ignore everything under `REMOVE_ME` - `ChatCompletions` and `Completions` model split - Adjusted optionality and nullability of fields
Follow up issue on this PR https://github.com/Azure/azure-rest-api-specs/pull/27683 We should include the option `stream-style-serialization: true` in the `tspconfig.yaml` file in the spec. Also remove `enable-sync-stack: true` as that is the default...
While implementing streaming in Java, I noticed in the JSON that there is usage data available that we could be deserializing. Maybe this is not the right PR to address...
**This is a WIP** Closes #39462 - Code gen based on spec repo [branch](https://github.com/Azure/azure-rest-api-specs/pull/28555) - `StreamTests` added for sync/async and Azure/non-Azure - SSE implementation for Assistants - Introduction of `StreamUpdate`...
### Expected behavior Releases should supply `jar` files where possible. Also, wherever Rx is used it should be optional and there should be a coroutine based alternative. ### Actual behavior...
Once the spec correction introduced after the resolution of [this issue](https://github.com/Azure/azure-rest-api-specs/issues/28905) is in place, add the custom code necessary to write an API surface that uses only `FileDetails` asserting `filename`...