> Not registering component style `val Style`, as only top-level component styles are supported a...

# kobweb

[Filip Wiesner]

Not registering component style val Style, as only top-level component styles are supported at this time

I was trying to make namespace for variants with top-level object 😢

[David Herman]

Yeah I want to allow object namespacing eventually, but keep in mind the names would still need to be globally unique

[Filip Wiesner]

And what is the reason for this restriction? That objects are lazily initialized?

[David Herman]

Oh, just code complexity

[David Herman]

Er wait

[David Herman]

You mean the name restriction?

[Filip Wiesner]

Nono, the

Not registering component style val Style, as only top-level component styles are supported at this time

[David Herman]

Yes that's just laziness

[Filip Wiesner]

😄

[Filip Wiesner]

Fair enough

[David Herman]

Basically the code I have now needs to check that the property is a singleton

[David Herman]

If defined at the top level, that's fine! We're done

[David Herman]

If it's defined in a class or in a method, that's not ok

[David Herman]

But I should check that IF I have parents AND of they are all objects, that should be ok. Then I have to pass the fully qualified path (including objects) on

[Filip Wiesner]

Ah, makes sense. I thought you need all the styles executed eagerly and objects are problematic

[David Herman]

After you run kobweb run do a search in your build directory for main.kt

[David Herman]

You'll see what I'm doing then 🙈

[Filip Wiesner]

Oooh, I see. You register everything on start to global context

[David Herman]

Yep!! 🔨