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 import of an OpenAPI specification in YAML format leads to an incorrect transformation of path parameters.
An OpenAPI specification such as /users/{id}
should normally read as follows in Bruno: /users/:id
In fact, the imported request url contains the parameter specification in curly brackets (i.e. still in the form /users/{id}) and the parameter concerned is also listed in the Bruno GUI under Params/Path.
If the request is sent, the variable in the request url is not replaced.
.yaml file to reproduce the behaviour
openapi: 3.0.0
info:
title: Sample API
version: 0.1.9
servers:
- url: http://api.example.com/v1
description: Optional server description, e.g. Main (production) server
paths:
/users/{id}:
get:
parameters:
- in: path
name: id
required: true
schema:
type: array
items:
type: integer
minItems: 1
style: matrix
explode: true
- in: query
name: metadata
schema:
type: boolean
# Using the default serialization for query parameters:
# style=form, explode=false, allowReserved=false
responses:
'200':
description: A list of users
Description
The import of an OpenAPI specification in YAML format leads to an incorrect transformation of path parameters.
An OpenAPI specification such as
/users/{id}
should normally read as follows in Bruno:
/users/:id
In fact, the imported request url contains the parameter specification in curly brackets (i.e. still in the form
/users/{id}
) and the parameter concerned is also listed in the Bruno GUI under Params/Path.If the request is sent, the variable in the request url is not replaced.
.yaml file to reproduce the behaviour
Originally posted by @epestela in #2506 (comment)
The text was updated successfully, but these errors were encountered: