openapi: method with same URL and different path parameters name result in 405

[robko23]

Expected Behavior

Both endpoints should return 200 OK

Actual Behavior

When having two endpoints on the same URL with different path parameters names result in one of them returning 200 OK and the other one 405 Method Not Allowed. It seems that the order of the functions does not matter, the GET method always gets the 405.
This issue is related to #429 but since that issue is closed and I cannot reopen it I'am opening a new one.

Steps to Reproduce the Problem

I have created a minimal reproduction of this issue repository: https://github.com/robko23/poem-openapi-routing-issue/tree/master

Specifications

• Version: [email protected] [email protected]
• Platform: GNU/Linux 6.12
• Subsystem: N/A

[robko23]

So as I was investigating further, I found out that the issue #429 was fixed by 78fb112. (change route_table from HashMap<String, HashMap<Method, ...>> to HashMap<Method, HashMap<String,...>>)
Then there was another issue ( #489 ) which was resolved by 9876172. (change route_table back to HashMap<String, HashMap<Method, ...>>
However these issues seem to be mutually exclusive and the latter commit reverted the fix by the former commit.
Kinda tricky situation. Any ideas how to solve this?

[robko23]

So I have an idea that this could be resolved by renaming the path to normalize param names.
eg. /hello/:param -> /hello/:param0, /hello/:another_param -> /hello/:param0.

This would create same entry in the routing table and it could resolve the issue. It could be "injecting" #[oai(name = "param{i}")] in the function signature.

I can look into this on the weekend and send PR to resolve this, but a small guidance would be appreciated.

I tried inserting format!("param{i}") here, but that did not work.

poem/poem-openapi-derive/src/utils.rs

Lines 127 to 132 in 658f7de

	oai_path.push_str("/{");
	oai_path.push_str(var);
	oai_path.push('}');
	new_path.push_str("/:");
	new_path.push_str(var);

Then I tried changing this

poem/poem-openapi-derive/src/api.rs

Lines 278 to 282 in 658f7de

	let pname = format_ident!("p{}", i);
	let param_name = operation_param
	.name
	.clone()
	.unwrap_or_else(|| arg_ident.unraw().to_string());

like this

let param_name = format!("param{i}");

but that didn't work either.
However I think that I'm on the right track.
I just need to rename the entry in the routing table and then change this

poem/poem-openapi-derive/src/api.rs

Lines 351 to 355 in 658f7de

	let mut param_opts = #crate_name::ExtractParamOptions {
	name: #param_name,
	default_value: #default_value,
	example_value: #example_value,
	explode: #explode,

to extract from the param{i} while keeping the openapi param name in meta and the variable name in method signature