Replies: 2 comments 2 replies
-
it is an excellent idea, I have the same feeling today about it being hard to change something. So we should do something that converts openapi format to moclojer specs. if they provide moclojer spec it will run as is. |
Beta Was this translation helpful? Give feedback.
-
I would double check if the current format of moclojer grants us a simplier conversion to the server routes, if it is the case I would remove the step to convert to openapi, plug the directly the moclojer spec into the server route. Later create a namespace that is responsible to convert openapi -> moclojer (this could be even a lib) and integrate this back into moclojer. |
Beta Was this translation helpful? Give feedback.
-
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).
Beta Was this translation helpful? Give feedback.
All reactions