It looks like Radix changed their way of making sub-menus.
Previously, to make a submenu, you would add a DropdownMenu.Root inside of an existing one. However, they now seem to use a Sub, SubTrigger, and SubContent as seen here.
I can see their reasoning here. The new API is much clearer. It's just a bit annoying to have to maintain parity, but it's probably the right move.
This is a breaking change from Radix v1, so chances are, I have to build these features before releasing zeego v1.
If anyone wants to submit a PR for these, it would be awesome. It would require:
installing direct dependencies of Radix UI's dropdown/context menus into zeego
adding Web/iOS/Android files for each Sub* element. Web will be easy; the others require understanding how Zeego maps children mostly.
It looks like Radix changed their way of making sub-menus.
Previously, to make a submenu, you would add a
DropdownMenu.Root
inside of an existing one. However, they now seem to use aSub
,SubTrigger
, andSubContent
as seen here.I can see their reasoning here. The new API is much clearer. It's just a bit annoying to have to maintain parity, but it's probably the right move.
This is a breaking change from Radix v1, so chances are, I have to build these features before releasing
zeego
v1.If anyone wants to submit a PR for these, it would be awesome. It would require:
zeego
Sub*
element. Web will be easy; the others require understanding how Zeego maps children mostly.