-
Notifications
You must be signed in to change notification settings - Fork 352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hyphenless followup #1192
Hyphenless followup #1192
Conversation
…prism into fix/hyphenated_query_params
…prism into fix/hyphenated_query_params # Conflicts: # test-harness/specs/content-negotiation/E2E-Accept-Content-Negotiation-AC-14.oas2.txt
…prism into fix/hyphenated_query_params
ac4e051
to
b32a51e
Compare
bbb3e25
to
13f5244
Compare
4b048e2
to
a150a8d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aren't we loosing data with current approach?
Consider this spec:
openapi: 3.0.2
paths:
/pet:
get:
parameters:
- in: query
name: pet-id
required: true
schema:
type: number
- in: query
name: petid
required: true
schema:
type: number
responses:
200:
description: ok
content:
application/json:
example: "ok"
This turns into:
[5:32:33 PM] › [CLI] ℹ info GET http://127.0.0.1:4010/pet?petid=834.7748617345209
We have lost pet-id
param because after removing hyphens it looked the same as petid
.
Constructive part:
I guess we should have two paths. One for hyphen-full params and second for hyphen-less ones. Last step will merge both results into single URL.
85202ab
to
c625141
Compare
c625141
to
1279e7c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor thing and ship it!
Co-authored-by: Karol Maciaszek <karol@maciaszek.pl>
Update the library and make it great again with dashes
P.S: Damn OpenAPI 3.
Closes #1191