importing components instead of one big global namespace

[LucidDan]

I've started using cotton relatively recently, and I'm already running into a problem, but not so much a technical one as an organisational one: my component names get quite long, due to all the folders I'm using the organise things. (a non-contrived example might be something like <c-twui.navbar.menu.item>, which is manageable but getting a bit long already).

I wonder if there has been any consideration of the idea of "importing" the components you're going to use.

e.g. perhaps something like:

{% cotton PageLayout="layouts/web_app_page.html" Header="tailwindui/application/header.html" %}
<PageLayout>
  <Header>
    <h1>This is the page</h1>
  </Header>
</PageLayout>

It'd be nice to be able to choose arbitrary html tag names like the above, but I'd also be totally fine if it still required the 'c-' prefix instead, I haven't dug through the loader code to understand the implications/limitations.

This seems like it would help, and could probably coexist with the global namespace without any issues.

However, please feel free to convince me of why its a terrible idea, instead. ;-)

[wrabit]

Hi @LucidDan thanks for the suggestion. I think generally the complexity it will introduce in the codebase may not be worth the benefit...

It doesn't sound like <c-twui.navbar.menu.item> is something you would need to reach for that often and once coded once, you'll maybe only see <c-nav /> or similar from your more repetitive views.