🤗 [Question]: V3: ctx.Render not longer accepts types other than fibre.Map

[m13t]

Question Description

I'm curious why the API for the fiber context no longer accepts the any type for render binding parameters and only accepts fiber.Map?

The abstracted template engines still support bind parameters allowing the passing of structs (or indeed a map) so I'm wondering if there are plans to change the template engine implementation to match too?

I feel like migrating from V2 to V3 with this change will result in a lot of unnecessary refactoring for users where structs that are used throughout an application lifecycle as well as being passed to templates, now need to be converted to a map structure.

Code Snippet (optional)

No response

Checklist:

• I agree to follow Fiber's Code of Conduct.
• I have checked for existing issues that describe my questions prior to opening this one.
• I understand that improperly formatted questions may be closed without explanation.

[welcome]

Thanks for opening your first issue here! 🎉 Be sure to follow the issue template! If you need help or want to chat with us, join us on Discord https://gofiber.io/discord