Open chrisdmacrae opened 6 years ago
I don't assume it would be too hard to do but we might need to decouple a few pieces to make it easier to maintain after this is done because this forces a parser split.
I'm not against doing this, I'm not against even making parent
an alias of identifier
for all other types of menus too (considering the context's it could be used in,) and then eventually in another version further down the line making parent
and identifier
strict contexts (parent
must have an identifier
that exists, and identifier
is used to create a context.)
I'll see what I can work out if you want.
@envygeeks thanks for the honesty!
This would be really great; it seems to be the way most users try to use these menus, and then learn to do it the other way.
Let me know if there's anything I can do to help facilitate this. 👍
@envygeeks curious to know if you think the following is possible:
Currently, to handle nested items, you would do something like this:
It would be nice, from an information architecture perspective, to also be able to do: