-
Notifications
You must be signed in to change notification settings - Fork 782
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
Sharing functions between constraint templates #1204
Comments
There is a static linking option available on constraintTemplates via the That's all that is supported for now. Dynamic linking can result in dependency version conflicts so we have avoided a provision for those. |
libs defined by one constraintTemplates can be accessed by that constraintTemplates only or are they shared between constraint templates? |
They can only be accessed by the one constraint template. Shared libraries have a number of issues:
The goal of "libs" was to make it a bit easier to leverage the developer advantages that shared libraries have while avoiding the operational liabilities by providing an easy way to "statically link" code (borrowing this term from C) |
@maxsmythe thanks for the information. I guess I will just work with that for now. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
Is there some way to share some basic functions between constraintTemplates? e.g a method to get nested field or even simple checks to identify the kind of a resource?
The text was updated successfully, but these errors were encountered: