Problem: middleware to append trailing slash should not be needed #13
Comments
sevein
added a commit
that referenced
this issue
Oct 17, 2024
This commit fixes #13 since kiota 1.19.0 included the fix with trailing slashes in the OpenAPI.NET repo (release 1.6.22). `appendTrailingSlashHandler` is removed because the generated client is now including trailing slashes as expected by Archivematica Storage Service.
sevein
added a commit
that referenced
this issue
Oct 17, 2024
This commit fixes #13 since kiota 1.19.0 included the fix with trailing slashes in the OpenAPI.NET repo (release 1.6.22). `appendTrailingSlashHandler` is removed because the generated client is now including trailing slashes as expected by Archivematica Storage Service. All tests under the root and example modules are passing with the handler removed.
sevein
added a commit
that referenced
this issue
Oct 17, 2024
This commit fixes #13 since kiota 1.19.0 included the fix with trailing slashes in the OpenAPI.NET repo (release 1.6.22). `appendTrailingSlashHandler` is removed because the generated client is now including trailing slashes as expected by Archivematica Storage Service. All tests under the root and example modules are passing with the handler removed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We started using
appendTrailingSlashHandlerbecause @typespec/http was unable to describe paths with a trailing slash, but it was fixed in v0.58.0. However the trailing slash is also dropped by Kiota when generating the Go client, see microsoft/kiota#4291 for more details. We'll have to rely on the middleware while this issue exists.The text was updated successfully, but these errors were encountered: