-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with Recognition of API path in Tapir version 10.4.1 #3702
Comments
I think we'll need more detail to understand what's the problem :) From what version to which one did you update? |
It has been quite a while since we last updated the version. Specifically, we were using version 0.19.4 before updating to the latest release. the issue is we have two end points (importJobs) and (import-jobs), before updating the version both 2 end points were working fine, but after updating all the test related to (import-jobs) end point failed. I changed the (import-jobs) to (import-job) and that worked fine, so I am wondering what can be the issue? here is the piece of code I'm referring val importJobs: EndpointTypeAuthInQuery[Unit, Set[ImportJob]] = |
I tested an endpoint using an |
would you please try it with having 2 endpoints at the same time, |
Sure, works fine: import sttp.tapir.*
import sttp.tapir.server.netty.sync.{Id, NettySyncServer}
object HelloWorldNettySyncServer extends App:
val e1 = endpoint.get
.in("import-jobs")
.out(stringBody)
.serverLogicSuccess[Id](_ => "1")
val e2 = endpoint.get
.in("importJobs")
.out(stringBody)
.serverLogicSuccess[Id](_ => "2")
NettySyncServer().addEndpoint(e1).addEndpoint(e2).startAndWait() test:
|
We encountered an issue recognizing our endpoint named 'import-jobs' after updating to the latest Tapir version. As a result, all tests for this endpoint consistently fail and return a 405 error. We have questions to find out why Tapir is unable to recognize this endpoint following the update.
The text was updated successfully, but these errors were encountered: