Properly register middlewares when using NewGroupPath about atreugo HOT 5 CLOSED

Awesome. Thanks for the feature.

from atreugo.

Hi @teja42,

Sorry for delayed answer, i have been on vacation.

The authentication middleware must be executed in the two group paths (AuthRouter and UploadRouter) due to you are registering on main router not in group router. So independently, if you declare the auth middleware before or after the group routers or in another sub-package, the execution always be the same, don't mind the declaration order in the code, just the UseAfter or UseBefore.

Execution chain:

1. Before middleware (Server.Router.UseBefore)
2. Before middleware (AuthRouter.UseBefore, UploadRouter.UseBefore, ...)
3. Before filter
4. View
5. After filter
6. After middleware (AuthRouter.UseAfter, UploadRouter.UseAfter, ...)
7. After middleware (Server.Router.UseAfter)

Because you want execute the authentication middleware in all paths, group paths, etc, right?

from atreugo.

Sorry for the delayed response

I DONT want the middleware to run for paths start with /auth
I WANT the middleware to run for paths that don't start with /auth

What I ended up doing was I registered the middleware first and if the path starts with /auth then
I called ctx.Next(). If not I performed the authentication and did accordingly. This approach works. Suggest me If there is a better one.

from atreugo.

At now it's the best solution

But i'm thinking in a new method to simplify that.

Soon, it could be available.

Thanks!

from atreugo.

Hi @teja42,

I've been released a new version v10.3.0

I added support for skip middlewares in groups and views 🎉

from atreugo.