I've encountered an inconsistency in the API response for the /v1/workspace/{slug} endpoint. According to the example provided in the swagger documentation, the response should be a single workspace object:
However, in my testing using the API in C# and AI-powered tools to generate client calling code, I've consistently received an array of (one) workspace as the response, regardless of the slug provided.
Reproduction Steps:
Use the /v1/workspace/{slug} endpoint with a valid slug.
Observe the response.
Expected Behavior:
A single workspace object, as documented.
Actual Behavior:
An array of one workspace.
Environment:
Docker 1.2.4
Desktop v1.6.8
Additional Information:
I've created a pull request with a proposed fix for this issue. If considered, it can be merged to update the documentation and ensure consistency in the API response.
Please let me know if this meets your requirements or if you need any further changes!
Description
I've encountered an inconsistency in the API response for the
/v1/workspace/{slug}
endpoint. According to the example provided in the swagger documentation, the response should be a single workspace object:However, in my testing using the API in C# and AI-powered tools to generate client calling code, I've consistently received an array of (one) workspace as the response, regardless of the slug provided.
Reproduction Steps:
/v1/workspace/{slug}
endpoint with a valid slug.Expected Behavior: A single workspace object, as documented.
Actual Behavior: An array of one workspace.
Environment:
Additional Information: I've created a pull request with a proposed fix for this issue. If considered, it can be merged to update the documentation and ensure consistency in the API response.
Please let me know if this meets your requirements or if you need any further changes!