Skip to content
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

Consumes - application/json not being passed to APIClient #62

Open
MumblesNZ opened this issue Jul 2, 2018 · 2 comments
Open

Consumes - application/json not being passed to APIClient #62

MumblesNZ opened this issue Jul 2, 2018 · 2 comments
Assignees
Labels
bug Some problem (breaking)
Milestone

Comments

@MumblesNZ
Copy link

Hello,

Just wondering if it's intended that the swagger property:

 "consumes": [
                    "application/json"
                ]

is meant to be ignored when generated the API client? I assumed a header would of been generated & applied to API services which have this property? Right now we are adding it to the NGModule as a universal header, but some API Client calls don't use application/json.

Is this intended behaviour or a bug?

Thanks =).

@vmasek
Copy link
Member

vmasek commented Jul 2, 2018

Thanks for the report, it is probably not intended, we'll investigate that.

@vmasek vmasek added the bug Some problem (breaking) label Jul 2, 2018
@vmasek vmasek self-assigned this Jul 2, 2018
@vmasek
Copy link
Member

vmasek commented Sep 1, 2018

The whole generation of what API consumes and returns needs to be refactored along with OpenAPI 3 spec compliance.

@vmasek vmasek added this to the 5.0 milestone Sep 1, 2018
@vmasek vmasek modified the milestones: 5.0, 4.x Feb 6, 2020
@vmasek vmasek modified the milestones: 4.x, 5.x Dec 19, 2020
@vmasek vmasek moved this to To do in Main board Aug 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Some problem (breaking)
Projects
Status: To do
Development

No branches or pull requests

2 participants