Handling file upload

[sdil]

How do I handle file upload in Fuego? From my understanding, file upload has to use multipart/form-data request but there's a way to write OpenAPI spec for that https://swagger.io/docs/specification/v3_0/describing-request-body/multipart-requests/

Does Fuego support this and can it produce correct OpenAPI spec for this endpoint? It seems like data serialization/deserialization in Fuego does not support multipart/form-data request.

I tried to create 1 endpoint that accepts binary file that looks like below:

func uploadFileHandler(c fuego.ContextWithBody[[]byte]) (any, error) {
	_, err := c.Body()
	if err != nil {
		return nil, err
	}

	return "ok", nil
}

When I tried to make a curl request, I get the following:

$ curl -X POST http://localhost:8000/expenses/upload \
     -F "[email protected]"
curl: (55) Send failure: Broken pipe

And I get observe the following error in the log:

11:54:11 ERR [email protected]/errors.go:183 Error Decoding Failed status=400 detail="cannot decode request body: invalid character '-' in numeric literal" error="invalid character '-' in numeric literal"

Ideally, I want to be able to upload multiple files into the server.

[EwenQuim]

Hi @sdil !

For the moment, Fuego doesn't support file uploads and multi file upload. Please use fuego.GetStd to use a standard handler and this tutorial.

We'll definitely work on that ;)

[sdil]

@EwenQuim is there is a way to document that endpoint in the openapi spec using fuego?

[hiddenmarten]

@EwenQuim @sdil I'll try to add one more example if you guys don't mind.

My main concern about current file uploading using []bytes way is that it would be fully stored in memory in the process of receiving. I'd prefer to have a chance to get a file with a stream for both multipart and octet-stream. Hopefully, I'll figure it out if it's possible. Also, I would appreciate your help if there is any, outside of fuego.GetStd.

[dylanhitt]

I’m willing to review a POC of this btw. My day job is probably gonna need this soon as well.