You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The path is appended (no relative URL resolution) to the expanded URL from the Server Object’s url field in order to construct the full URL
Which is not the way ketting implements it since it uses URL resolution.
Exemple :
const client = new Client('https://domain.com/api');
client.go('/projects/d123');
// Will go to https://domain.com/projects/d123
// According to OAS, should go to : https://domain.com/api/projects/d123
What to you think ?
The text was updated successfully, but these errors were encountered:
From OAS 3.1 spec :
Which is not the way ketting implements it since it uses URL resolution.
Exemple :
What to you think ?
The text was updated successfully, but these errors were encountered: