Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out what to do about child elements #13

Open
marknutter opened this issue Dec 12, 2015 · 1 comment
Open

Figure out what to do about child elements #13

marknutter opened this issue Dec 12, 2015 · 1 comment
Labels

Comments

@marknutter
Copy link
Owner

What should be done about child nodes? As it stands right now, they always have to have unique tags, which means having a unique tag, tag+class, or tag+id. Should we move to having the children node have an array value, or keep them as nested objects? What to do about sorting? Is it too much to ask that unique node names be used?

@marknutter
Copy link
Owner Author

Allow the defining of children as arrays but under the hood convert the children array to an object with unique ids or classes. Otherwise, maybe keep them arrays but using NuxQuery provide a syntax for selecting the nth child, similar to jQuery's div:eq(n) syntax

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant