Incorrect routing when the URL differs by a static query param only
The example below, while is a valid smithy, fails to be routed correctly by smithy4s. The routing mechanism uses a combination of HTTP method and path, where path is just a part without query params. As a result, one of these endpoint will be receiving both types of requests.
$version: "2"
namespace example
use alloy#simpleRestJson
@simpleRestJson
service ExampleService {
version: "1.0.0",
operations: [GetQuery, GetQueryStatic]
}
@http(method: "GET", uri: "/get-query")
operation GetQuery {
}
@http(method: "GET", uri: "/get-query?static")
operation GetQueryStatic {
}
mmm interesting. We need to define some form of ordering of uri patterns.
for ordering, #1567 - https://smithy.io/2.0/spec/http-bindings.html#specificity-routing Example 2 shows what to do when ? is present.
worth noting, we do seemingly support static query params (HttpEndpoint has staticQueryParams, which I didn't know).
so maybe this is just a dupe of #1567 after all?
Closed in #1743, specificity will be closed in #1766