RW

you can ask in the https://github.com/fasthttp/websocket project, if necessary you can add something there, so that you can access the status faster

Not really a bug, until now our methodic does not allow custom methods

Maybe we can provide a method where you can register the custom request methods

```go func main() { app := fiber.New() sub := fiber.New() sub.Get("/", func(c *fiber.Ctx) error { return c.JSON("this is sub app") }) app.Mount("/sub", sub) //

@wangjq4214 > but i don't know if this will have negative effects later, because after this command you actually think that something is transferred that wasn't transferred yet -> if...

> @ReneWerner87 and @wangjq4214 , this problem was resolved on v3-alpha branch. Solution: Router stacks should be registered on buildTree. [see also](https://github.com/gofiber/fiber/blob/v3-alpha/core.go#L379) good to know, but we are still quite...

Yes of course but that does not help me answer my question If you add the routes later and then add hooks that work when the route is registered, it...

sorry very busy week, will answer tomorrow

current implementation seems to be okay - [ ] please also update the documentation repository feature will be in the next release

@rafimuhammad01 pls check the last comments