-
Notifications
You must be signed in to change notification settings - Fork 6k
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
[All] Add a supportsMixin property to codegens #3636
Comments
Apologies for the delay in responding – have been swamped both at work and at home. For the first bullet I think you meant “currently if supportsInheritance is false, the properties from parent and interfaces will not be included in vars.” I see what you mean in the Java case. It is true that Mustache templates, being logic-less, require all business logic to be implemented by the caller. If you’re confident that your change can address the requirements of JavaScript, Java and other languages whilst preserving or rectifying existing (mis-)behaviour as appropriate then I wish you good luck with the PR. Cheers, --A From: Christophe Bornet [mailto:notifications@github.com]
The consequence is that since we don't have the interface properties in vars, we have to duplicate the code everywhere in the template to include both vars and interfaceModels.allVars @wing328 https://github.com/wing328 I can do the PR if OK. cc @demonfiddler https://github.com/demonfiddler — This email has been scanned by BullGuard antivirus protection. |
PR merged into master |
The consequence is that since we don't have the interface properties in vars, we have to duplicate the code everywhere in the template to include both vars and interfaceModels.allVars
This could be mitigated by putting some parts of the code in imported templates but that would also make the template much harder to read.
So my idea is to add a supportsMixin property for languages that can use it (eg. Javascript)
@wing328 I can do the PR if OK.
cc @demonfiddler
The text was updated successfully, but these errors were encountered: