Skip to content

Conversation

@jamietanna
Copy link
Member

As noted in #1469, when registering custom middleware for Fiber, the
server panics.

This is because Fiber expects a specific type, but accepts:

func (fiber.Router) Use(args ...interface{}) fiber.Router

This resolves this by ensuring that we always wrap our middleware
functions in a Fiber-compatible handler.

We also add a regression test for this use case.

Closes #1469.

Co-authored-by: emdfonseca emdfonseca@users.noreply.github.com

@jamietanna jamietanna added bug Something isn't working wontfix This will not be worked on server:fiber labels May 18, 2024
As noted in #1469, when registering custom middleware for Fiber, the
server panics.

This is because Fiber expects a specific type, but accepts:

    func (fiber.Router) Use(args ...interface{}) fiber.Router

This resolves this by ensuring that we always wrap our middleware
functions in a Fiber-compatible handler.

We also add a regression test for this use case.

Closes #1469.

Co-authored-by: emdfonseca <emdfonseca@users.noreply.github.com>
@jamietanna jamietanna merged commit 26f8257 into master May 18, 2024
@jamietanna jamietanna deleted the defect/issue1469 branch September 19, 2024 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working server:fiber wontfix This will not be worked on

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Panic in fiber's server when registering handlers with middleware

2 participants