-
I note you have released an API, but it doesn't currently include OpenAPI-compliant YAML or JSON documents that describe service endpoints and call patterns for REST-ful interaction.
-
According to the [official API docs](https://developer.xero.com/documentation/api/assets/assets#get-assets), getting a single asset should include a "description" field. However, the gem does not supp…
-
-
### Current Behavior
When sending a PATCH request to the https://panel.[MY DOMAIN]/api/application/nodes/1 endpoint, the description in the body isn't updated. There response indicates, that everyt…
-
-
**Describe the bug**
If a service does not change ID and updates description metadata, i.e. `apiml.catalog.tile.description` and/or `apiml.service.description`, API Catalog may show the cached descri…
-
> In the future, I think that we want to automatically remove `https://mui.com/` from those links to have relative URLs.
_Originally posted by @oliviertassinari in https://github.com/mui/material-u…
-
-
### Prerequisites
- [X] I have carried out troubleshooting steps and I believe I have found a bug.
- [X] I have searched for similar bugs in both open and closed issues and cannot find a duplicate.
…
-
**What would you like to be added**:
Ideally the API spec should have more information about RegEx validation, for example where it came from or what it's based on. This should be visible in go type …