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
README: Migrating from V1? #348
Comments
@jackstrosahl it should generate more or less the same code as with v1. The overhaul with v2 was more about internal architecture. There are command-line options that more or less generate the same code as with v1. If you had custom templates you were using previously, you'll likely need to completely rewrite those, as it's been drastically changed how the templates work. Also, I would hold off on rewriting templates for now, as I have a practically finished commit that once again redoes how templates are generated/applied. However, the new format for custom templates is a format that has an interface that I plan to support for some time. |
Oh, sorry. If you're having difficulty regenerating code using v2, please drop a specific schema/query example and I'll be glad to help you debug what the issue is. |
@kenshaw Thanks for the quick response, I am using custom templates I meant to specify that. I'll hold off on rewriting those for now though. |
@jackstrosahl We just pushed the semi-final changes for making templates completely dynamic. Take a look at the latest code, and let us know what you think. |
@kenshaw Great! Haven't tested yet but I'm assuming the templates don't support third-party Go modules due to yaegi. Is this correct? If not, how did you get it working without extract? |
Could there be some documentation on migrating from V1 to V2? I need to do this but have just been putting it off and using the old version. If it's not wanted to be in the readme any tips here are welcome.
The text was updated successfully, but these errors were encountered: