replace *fiber.App with fiber.Router Interface

[create-go-app]

replace *fiber.App with fiber.Router Interface

[hotrungnhan]

Sincerely thanks for explain me how this template work , you've show me a great point of view.

[welcome]

Thanks for opening your first issue here! 🎉 Be sure to follow the issue template!

[koddr]

Hi,

I don't know why this option seems better to you, but I'll try to explain by example why I chose this way of organizing routes in the application. In the world of Go, it is a good thing to make fallback versions for REST API methods that are outdated but still in demand by users.

For this reason, to easily support two different versions of the API in one Fiber application, I will simply create another route file in which I set the next version of the API, like this:

// ./pkg/routes/public_routes_v2.go

// PublicRoutesV2 func for describe group of public routes for API v2.
func PublicRoutesV2(a *fiber.App) {
	// Create routes group.
	route := a.Group("/api/v2")

	// Routes for GET method:
	route.Get("/books", controllers.GetBooksV2) // <-- get list of all books for API v2

        // ...
}

Note that all controllers for the new version of the API are also marked with the new names (with the ending V2 to make it easier to identify them).

And next, I will add this new routes group to the main.go, like this:

// ./main.go

// ...
func main() {
	// ...

	// Routes.
	// ...
	routes.PublicRoutesV2(app)  // <-- register a public routes with API v2 for app
	// ...
}

As you can see, this way of organizing code in Fiber application allows you to keep a fallback version (for v1 users) and add new routes to make changes to the v2 API. And most importantly, this way is absolutely transparent for understanding and subsequent writing of unit tests because everything lies in its place: the description of routes and their challenge. 😉

If you are more convenient to use the option you gave in the example, then you are absolutely free to use it in your application! But I hope I've explained to you my point of view on this application template and the decisions made in it.