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
Is your feature request related to a problem? Please describe:
When getting PkgPath and BaseSchema of kclTypes, the current apis (GetFullSchemaTypeMappingWithFilters) can only get from the pkg itself, instead of from a complete kcl.mod.
e.g.:
Given kcl.mod:
[package]
[dependencies]
mymod = { git = "https://domain/abc/mymod.git", tag = "v0.1.21" }
base = { git = "https://domain/def/base.git", tag = "v0.1.0-alpha.2" }
In catalog there is mymod.v1.DNSConfig, which inherits base.v1.GlobalConfiguration in the base pkg.
Problem1:
When getting kclType mymod.v1.DNSConfig, its PkgPath will be "main" instead of "v1".
Problem2:
If the kcl.mod in pkg catalog does not have dependency of pkg kam (which is wierd but it's actually working), the BaseSchema of kclType mymod.v1.DNSConfig will be nil.
Describe the feature you'd like:
Get schemas with proper PkgPath and BaseSchema from a given kcl.mod, including all dependencies
Feature Request
Is your feature request related to a problem? Please describe:
When getting PkgPath and BaseSchema of kclTypes, the current apis (GetFullSchemaTypeMappingWithFilters) can only get from the pkg itself, instead of from a complete kcl.mod.
e.g.:
Given kcl.mod:
In catalog there is mymod.v1.DNSConfig, which inherits base.v1.GlobalConfiguration in the base pkg.
Problem1:
When getting kclType mymod.v1.DNSConfig, its PkgPath will be "main" instead of "v1".
Problem2:
If the kcl.mod in pkg catalog does not have dependency of pkg kam (which is wierd but it's actually working), the BaseSchema of kclType mymod.v1.DNSConfig will be nil.
Describe the feature you'd like:
Get schemas with proper PkgPath and BaseSchema from a given kcl.mod, including all dependencies
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
The text was updated successfully, but these errors were encountered: