Skip to content

Resolution from baseUrl may comply to OAS spec ? #480

@remidewitte

Description

@remidewitte

From OAS 3.1 spec :

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 ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions