Add a controller layer to this framework if possible
like this:
https://beego.me/docs/intro/#the-execution-logic-of-beego
Thanks for opening your first issue here! ๐ Be sure to follow the issue template! If you need help or want to chat with us, join us on Discord https://gofiber.io/discord
Hi @Mahdihp I think fiber.Handler is already a controller layer. Could you provide more specific examples?
Add MVC Architecture like this :https://beego.me/docs/mvc/
Add MVC Architecture like this : https://github.com/kataras/iris/wiki/MVC
Could you show a code example @Mahdihp?
Aye @Mahdihp
I don't think that's a good idea. The goal of fiber is to be a framework as simple and minimalist as possible as expressjs is.
So adding an MVC architecture makes the framework more complexe for nothing. The goal is to let the user choose to organize himself as he wants. Currently you can choose to write your own app in MVC.
But maybe i'm wrong ?
In fact, the fiber-boilerplate uses MVC architecture.
And it tries its best to mimic laravel in terms of developer convenience, i
think you should check it out.q
On Sun, Aug 16, 2020, 05:05 Vincent Glize notifications@github.com wrote:
Aye @Mahdihp https://github.com/Mahdihp
I don't think that's a good idea. The goal of fiber is to be a framework
as simple and minimalist as possible as expressjs is.So adding an MVC architecture makes the framework more complexe for
nothing. The goal is to let the user choose to organize himself as he
wants. Currently you can choose to write your own app in MVC.But maybe i'm wrong ?
โ
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gofiber/fiber/issues/718#issuecomment-674451643, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANCVUDGK7MFQ3XEBAPHMHALSA4BCNANCNFSM4P2WYTVA
.
I'm closing this issue because I personally don't see any real benefit to implement MVC within the framework, like @Dumbeldor said: Fiber's goal is to be simple and minimalistic but flexible, so the user can decide if he wants to use the MVC architecture.
Thanks for your suggestion though, PR's are always welcome!
Most helpful comment
I'm closing this issue because I personally don't see any real benefit to implement MVC within the framework, like @Dumbeldor said: Fiber's goal is to be simple and minimalistic but flexible, so the user can decide if he wants to use the MVC architecture.
Thanks for your suggestion though, PR's are always welcome!