You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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
andedn
) toopenapi
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).
The text was updated successfully, but these errors were encountered: