Chris Keathley

Thanks for the writeup @philliplongman. Its interesting that you're getting an httpoison error for this. I'll try to re-create this on my machine and see if I can figure out...

Thanks for the repo! I'll take a look. The reason we need to make an http request is due to how we communicate with the browser. We use a technology...

@tjshipe Does it work if you add `visible: false` to the selector you're using?

I'm not sure if I'll have time to go through and submit PRs for these but I'm available if you need to know about each query and what it will...

My main concern with `within` is that it'll be impossible to remember the order. I need to think about the idea of passing a `within` option. I wonder if we...

I've split off everything in problem 1 since its unrelated to the composition or nesting of queries. We can work on nesting as a separate task.

I've been thinking about this more. I think we want to use something like `nested_under` or `nested_in` or `child_of`. The arguments should be `nested_under(my_query, the_parent)`. The reason is because if...

After thinking about it a bit I think we should go with `child_of`. I think thats the most semantically correct word. It communicates what the relationship is between these two...

Ah I see what you're saying...ok, `nested_under` is the best alternative that I've come up with so far. I suppose we could make it more explicit by saying `nested(selector, under:...

I've been thinking for a while about the best way to support customizable error messages. So far I haven't come up with anything that I really love. I was considering...