You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello there, again thank you very much for a beautiful project.
I'm just filing an issue to keep track of it, though totally not crucial:
Seems that the dependencies can be fetched twice.
kcl mod update
adding 'file-manifests' with version '0.1.0'
downloading 'some-org/iaas-kcl-modules/file-manifests:0.1.0' from 'ghcr.io/some-org/iaas-kcl-modules/file-manifests:0.1.0'
downloading 'some-org/iaas-kcl-modules/file-manifests:0.1.0' from 'ghcr.io/some-org/iaas-kcl-modules/file-manifests:0.1.0'
Modules with local dependencies do not work.
Let's admit we have a remote module with the mod file (if I'm not wrong with the actual syntax) as bellow:
[package]
name = "file-manifets"
edition = "v0.8.0"
version = "0.1.0"
[dependencies]
k8s = { oci = "oci://ghcr.io/kcl-lang/k8s", tag = "1.28" }
names = { path = "../names" }
The above package after published is broken, since kcl mod later on tries to resolve names and this doesn't work... Something should be decided regarding this, like would it or not make sense to vendor local dependencies together with the package.
The text was updated successfully, but these errors were encountered:
Hello there, again thank you very much for a beautiful project.
I'm just filing an issue to keep track of it, though totally not crucial:
Let's admit we have a remote module with the mod file (if I'm not wrong with the actual syntax) as bellow:
The above package after published is broken, since kcl mod later on tries to resolve names and this doesn't work... Something should be decided regarding this, like would it or not make sense to vendor local dependencies together with the package.
The text was updated successfully, but these errors were encountered: