M. Efe Çetin

> It does not provide the full options and configurability of the filesystem middleware. > > Eg directory listing Can you provide an example/code snippet

> https://github.com/gofiber/fiber/blob/master/middleware/filesystem/filesystem.go#L38 Why to want filesystem middleware for templating? It's just for serving files

> sure why not, I am currently not clear about the benefits, but I hope everything we need we can realize with it I think it's important thing to be...

> You mean that we use more open source tools? Because with the kind of generation it doesn't really change that we are more open source. Yes but it's not...

> `users.0.name=john&users.1.name=jack` looks strange, I think it must be like `users[0][“name”]=john&users[1][“name”]=jack` They're both supported

Overridden by https://github.com/gofiber/fiber/pull/2117

I'm going to start implementing router in the next weeks :rocket:

I preapred a list of tasks. What do you think @trim21 - Map binding (will check it asap) - Multipart file binding - Better nested binding behavior like current binding...

> I'm woking on multipart file binding now. > > Why do we add a map binding insteading of adding a util function FasthttpArgsToMap(interface{VisitAll})map[string]...? I think it would be more...

I think we should add GetHeaders, GetRespHeaders, GetParams back. They are useful for something needs map. Should we add them into the ctx or Bind (like Bind().GetHeaders())? @ReneWerner87 @trim21