Interested in any updates

[jackdreillyvia]

First of all, thanks for taking the time to publish your work here, we've found it very valuable in putting structure and order into our API Design!

Have you evolved your work in this project in any manner? Particularly around OpenAPI 3.0 compatibility, we would be interested in trying, and contributing to any work along the lines of Rapier.

Thanks again for the very cool project

[mpnally]

Thanks, Jack. I have not worked on this in a long time. To be honest, the Python code is a bit of a mess. I have thought a few times of doing something simpler. Rapier is trying to be a bridge between the OpenAPI crowd, who are really doing a form of RPC, and ideas in REST. My idea for the "middle ground" was to allow for URIs of the form http://example.org/account/account-id/payment/payment-id, with an interpretation that adheres more closely to REST principles. This made Rapier more complex than I originally anticipated. I have lost enthusiasm for this sort of URL. If I were doing it over, I would only support URLs of the form http://example.org/payment-app/id. I would also support http://example.org/payment-app?account-id=account-url&amount=10, but I would not try to define my own grammar for the query string. A new version of Rapier with this limitation would be much simpler, and in my view the resulting APIs would be better, but it would not appeal to the OpenAPI crowd.