Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Client generated from API does not contain FileResponse

See original GitHub issue

I tried generating a C# Winx64 Client from API located at https://developer.allegro.pl/swagger.yaml using NSwag GUI. No matter which generation mode I choose, I always get code which references FileResponse in one of the methods but there’s no FileResponse class generated in the output. The offending API method /sale/dispute-attachments/{attachmentId} is described as returning type */*.

Issue Analytics

State:
Created 3 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

2reactions

Thieundcommented, Aug 11, 2020

I encountered the same error, but for Typescript client

0reactions

keleutos2022commented, Jan 17, 2023

Any news on this?

Top Results From Across the Web

How to handle FileResponse return type of Nswag methods

I am using Nswag to generate client library to consume an API created from .NET Core Application. Currently I am using actions that...

Custom Response - HTML, Stream, File, others - FastAPI

If you use a response class with no media type, FastAPI will expect your response to have no content, so it will not...

Request and response objects

Django uses request and response objects to pass state through the system. ... POST does not include file-upload information. See FILES . HttpRequest....

Describing Responses

An API can respond with various media types. JSON is the most common format for data exchange, but not the only one possible....

Responses

Responses. Starlette includes a few response classes that handle sending back the appropriate ASGI messages on the send channel.