I am working on a project using the fiber/v2 router, for a request mocking service. Now parameters passed via request body and query parameters are not an issue and handled easily. But here lies the problem with path parameters: Let’s say we have a basic endpoint like http://host.org:port/, I will denote this by “be”. Now for a URL like

be/invoke/param1/param2

where the user sending request has the option to send just param1 or param1 and param2 both, parsing looks like a difficult task. There can be many types of cases and it is definitely hard to generalize in my opinion. It would be great if people could help with this case and then we maybe can generalize the problem.

Of course we need not look on cases like:

be/invoke/param1/details/param2

This becomes much harder 😛

P.S. We are strictly trying to solve this problem in fiber because porting the entire thing to gin is not feasible, thanks.

I referred the Gin framework because they implement both Query and Path parameter parsing. But I was not very clear on how they were doing it and didn’t find example for more dynamic use cases.