I have an OData function as a part of my API with the following path:
/me/RecentCommunication(senderEmail='{senderEmail}'):
Shortly after I updated my spec to 3.1.0 an error "'path' must begin with '/' and be relative to an individual" occured. It is strange that error does not appear immediately but after a few minutes. I have never had any issues with this path before and it is OK on the older version of this API (OAS version 3.0.0). It seems to be related to '=' in the function path.
YAML is valid and this endpoint is displayed correctly in API doc. So it seems as a bug to me.
Q&A (please complete the following information)
Example Swagger/OpenAPI definition:
Describe the bug you're encountering
I have an OData function as a part of my API with the following path: /me/RecentCommunication(senderEmail='{senderEmail}'):
Shortly after I updated my spec to 3.1.0 an error "'path' must begin with '/' and be relative to an individual" occured. It is strange that error does not appear immediately but after a few minutes. I have never had any issues with this path before and it is OK on the older version of this API (OAS version 3.0.0). It seems to be related to '=' in the function path.
YAML is valid and this endpoint is displayed correctly in API doc. So it seems as a bug to me.
Any suggestions?
Screenshots