RW

Just know that later there will be questions or feature requests if the error messages we generate due to a mismatch are customizable. So we should create formatted strings for...

Or ask if we can customize the structure (json, xml, html) and the status code If a mismatch is detected, we should pass the error message which is composed of...

yes would go, but would not be quite optimal users will think that there is already a detection of which parameters do not match and expect this information to be...

 the c# feature also has a custom error message with the parameters that do not match

okay gladly, as long as this does not produce too many allocations, if we keep this data available that is acceptable performance and simplicity is fiber's recipe for success ->...

@goldalworming have a look at the code and i would try the code snippet ```go app.Get("/rerender", func(c *fiber.Ctx) error { engine.Reload(true) if err := engine.Load(); err != nil { panic(err)...

fail with "panic" or error? if you want your handlers to continue, you would have to catch these errors, react to them and ignore them in the flow and put...

> I just wanted to know if there is any short-circuiting kind of pattern available. no i think not @efectn @Trim21 any other ideas ?

thanks for the pull request, can you(@binhnguyenduc ) please add unittest for initializing with the new variant and some explanations in the README.md? after that i will merge it

@binhnguyenduc please check my last comment