-
Notifications
You must be signed in to change notification settings - Fork 33
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
Considerations for generating Ruby? #25
Comments
The current priority would be that schematic generate again some Go for the new API schema 😕 |
It's not generating against the current schema any longer? Shoot. Ack, it's too bad to hear about Ruby though! Feel free to close this out then, but we should still keep it mind as a possibility :) Thanks. |
I started working on fixing it, but haven't yet reach a satisfactory state. I do not totally exclude multi-language support, but that would requires smarter design too. |
@cyberdelia what about splitting schematic into different packages?
That way you could generate alternative cli's for Ruby/documentation/a server/... |
I though of that, generating a sort of AST and leaving language specificities to some kind of renderer, it's very much a pie in a sky right: since we can't resolve a JSON schema properly anymore. |
@cyberdelia do you have a list of the current issues resolving JSON schema? |
@ernesto-jimenez Mainly #29. |
@cyberdelia well, that bug is about failing with invalid JSON Schema :) |
@ernesto-jimenez Try using schematic against the heroku JSON schema. |
Hey @cyberdelia!
I've seen quite a few complaints around our current Ruby API client for V3, and am considering trying to replace it.
What do you think about generating Ruby code from Schematic? It seems like the main change required would be an extra set of templates. Are there any other considerations that you can imagine?
Thanks!
/cc @bgentry
The text was updated successfully, but these errors were encountered: