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

rethink element endpoints and grouping strategy #5

Open
CaptainN opened this issue May 22, 2013 · 0 comments
Open

rethink element endpoints and grouping strategy #5

CaptainN opened this issue May 22, 2013 · 0 comments

Comments

@CaptainN
Copy link
Member

To make the nested naming stuff easier to deal with, it might make sense to think about the bottom level elements differently when it comes to select boxes, and add a grouping mechanism for any elements that use the square bracket syntax. Currently, I've got the field extractor looking for selects first, then looping options, rather than looking for the bottom element - the options, then grouping them appropriately through a more generic grouping mechanism, which could apply to any grouped elements (using the php square bracket syntax). Selects would just be a version of grouping that works on DOM parenting instead of name based grouping.

Thinking about grouping this way fits the constraints of the request data (and therefor our DOM query options) better.

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

No branches or pull requests

1 participant