Why not keep Radix syntax of importing components?

[affenity]

Hi team.

I hope this has not been asked previously, and if so, feel free to link me to it.
I was wondering why Tremor doesn't utilize the same conventions as Radix in terms of syntax of imports/exports.

To illustrate what I mean, see the code sections below.

What we currently have:

import { DropdownMenu, DropdownMenuTrigger, DropdownMenuLabel, DropdownMenuContent } from "@...."

<DropdownMenu>
  <DropdownMenuTrigger></DropdownMenuTrigger>
  <DropdownMenuContent></DropdownMenuContent>
</DropdownMenu>

What I want/prefer:

import { DropdownMenu } from "@..."

<DropdownMenu.Root>
  <DropdownMenu.Trigger></DropdownMenu.Trigger>
  <DropdownMenu.Content></DropdownMenu.Content>
</Dropdown.Menu>

It may not seem obvious at first, but here are some points on why I prefer this syntax over the current one:

Readability & efficiency

• It improves readability and my efficiency writing custom code with Tremor as everything related to a Tremor component can be used with a simple "." while coding, instead of guessing or looking up the component or searching in the docs.
• It reduces mental overhead. I no longer need to read the entire component name in the code, while I'm in the "DropdownMenu context", I can just glance at the post-dot naming and understand.

Cleaner code - less imports
From

to

---

Hoping to learn more about this!

[severinlandolt]

Hi! This is just some leftover from the early days 2022. Might change in v4 :)