Skip to content
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

Reduce maintenance complexity caused by the OpenAPI specification #113

Closed
avelino opened this issue May 9, 2023 Discussed in #111 · 0 comments · Fixed by #121
Closed

Reduce maintenance complexity caused by the OpenAPI specification #113

avelino opened this issue May 9, 2023 Discussed in #111 · 0 comments · Fixed by #121

Comments

@avelino
Copy link
Member

avelino commented May 9, 2023

Discussed in #111

Originally posted by avelino May 5, 2023
When I look at the moclojer code I feel that we are building it wrong, it is hard to understand (especially the openapi package).

We need to make the code simpler and more readable, the way it now increases the barrier for new contributors to get in - if I (who started the project) having trouble understanding it, imagine who is just getting here

solution

Moclojer converts the moclojer specification (yaml and edn) to openapi format and the http server is built on top of the openapi specification - that's how it works today.

The proposal would be that moclojer supports "only" the moclojer spec and who wants to use openapi we do the conversion from openapi to moclojer spec.

This way, the moclojer spec will evolve in parallel with openapi (to run on moclojer).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment