Yuchao Yan
Yuchao Yan
@mattsp1290 I ping you in e-mail and you can share the http content/headers in that e-mail thread.
With https://github.com/Azure/azure-rest-api-specs/issues/25455#issuecomment-2147863985, I expect the response body format is like:  However, the examples are still:  It shows that the example is not recorded as I ask in https://github.com/Azure/azure-rest-api-specs/issues/25455#issuecomment-2147863985.
/check-enforcer override
(1) client and operation breaking change: - client signature `credential`, `subscription_id` has different order - client signature `base_url` is renamed to `endpoint`, and it is from positional to keyword-only -...
(2) file name change (may influence CLI): - `_xxx_enum.py` -> `_enum.py` - `_models_py3.py` -> `_models.py` - `_xx_operation.py` -> `_operations.py`
(3) other change: - can't set `api_version` in operation - no `case_insensitive_dict` - no `_convert_request` - no annotation for `cls` in docstring - no `metadata` for operation - [no `maxpagesize`...
Comparing with REST API call with `requests`, Python SDK can provide other function (e.g. authentication/customized policy/unified exception/...). Each way has pros/cons, and developers can choose any way they like to...
@yochananrachamim Thanks for the contribution!