[Bug] Wrong References for the module variable

[Peefy]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

In the konfig repo https://github.com/kcl-lang/konfig/blob/main/models/kube/frontend/job.k

2. What did you expect to see? (Required)

The right reference list

3. What did you see instead (Required)

4. What is your KCL components version? (Required)

v0.10.7

[dennybaa]

Possibly this one is related too, running v0.10.7:

import .providers  # module
resources = {
    #                         v
    #                  module
    "providers": providers.installProviders  # [Provider]
    #                              v
    #                        [Provider]
    "vault-config": providers.vaultConfig # error
}

35 |     "vault-config": providers.vaultConfig
   |                     ^ attribute 'vaultConfig' not found in '[Provider]'

Actually resource.providers definition at top of resources uses a locally set providers. From one side it's kinda expected and what it should be, but it used to work before. Please share what the actual future behavior should be?

[dennybaa]

Also, @Peefy please note that 0.10.7 behaves strange with modules, they appear exposed similarly to variables. However this one is unexpected, since the scope for import ... identifiers should be better file only, but not anymore...

• sub/use_to_config.k (import ..config)
• sub/main.k (import .config)

.
├── config.k
├── kcl.mod
├── kcl.mod.lock
├── main.k
└── sub
    ├── config.k
    ├── main.k
    └── use_top_config.k

This clashes with

   |
1 | import ..config
  | ^ the name 'config' is defined multiple times, 'config' must be defined only once

[Peefy]

Yes, some recent bug fixes have caused these regression errors. We will fix it later and release it in v0.10.8+ and v0.11.x