Florian Meriaux

Thanks for the answer. Indeed, it makes sense. Nevertheless I think it could be interesting and be an added value for Tapir to embed some REST API standards. Why not...

Indeed, the static part of Tapir meets a lot of REST standards. The problem with this implementation is that it is very restricted to a "static" use, which is consistent...

I will try to make an example of how we could use a `ResourceEndpoint` with different usage and you can give me your opinion :)

**I.** A first step could be to make methods implemented here public: https://github.com/softwaremill/tapir/blob/master/core/src/main/scalajvm/sttp/tapir/static/TapirStaticContentEndpoints.scala#L36 Why not in an object named for example `EndpointResourceIO` ? 📍 The goal would be to allow...

Within our team we also miss this behavior. If you feel that this behavior is not necessarily adapted to a "default" parameter, maybe you can simply give the possibility to...

I had the same thought about the deployment feature being deprecated. When you rummage around on the possibilities and the different writings, you see that nothing evolves anymore, and that...

If I have a bit of time, I'll try to make a PR 🙂 For the message: in my experience, logging tools (which parses the json) expect a single message....

Interesting, perhaps it would be a good idea to have an action parameter that allows you to complete the pattern by default? This would give us finer control over the...

I agree with your example of a non-list value. It's actually quite simple, I imagine, with Tapir, to validate the String and set a minimum length if necessary. However, in...

This is quite a special case I agree, my opinion is that the behavior should be: 1. Option's codec should manage the presence or absence of the parameter (none if...