We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Given the following setup:
PackageA/ -> depends on PackageC@1.1.0 PackageB/ -> depends on ../PackageA, PackageC@1.2.0
And PackageA has the following
// MyModule.pkl import "@packageC/Something.pkl" something: Something
Then usage from PackageB:
amends "@packageA/MyModule.pkl" import "@packageC/Something.pkl" something = new Something {}
This results in an incorrect type error in IntellijJ (one sees PackageC@1.1.0, another sees PackageC@1.2.0).
Screenshot of real life example:
This error can be seen in this commit: d238a01
And in file packages/k8s.contrib.crd/internal/ModuleGenerator.pkl
The text was updated successfully, but these errors were encountered:
Use local dependencies whenever possible
472a016
This is a workaround for two issues: * apple/pkl-intellij#23 * apple/pkl#414
Use local dependencies whenever possible (#50)
aa4b574
This is a workaround for two issues: * apple/pkl-intellij#23 * apple/pkl#414 Co-authored-by: The Pkl Team (automation) <pkl-oss@groups.apple.com>
No branches or pull requests
Given the following setup:
PackageA/ -> depends on PackageC@1.1.0
PackageB/ -> depends on ../PackageA, PackageC@1.2.0
And PackageA has the following
Then usage from PackageB:
This results in an incorrect type error in IntellijJ (one sees PackageC@1.1.0, another sees PackageC@1.2.0).
Screenshot of real life example:
This error can be seen in this commit: d238a01
And in file packages/k8s.contrib.crd/internal/ModuleGenerator.pkl
The text was updated successfully, but these errors were encountered: