David Sommers

So you still want to use: ``` ruby child :questions.available do attributes :id, :interview_id, :time end ``` Or are you asking about how you can manipulate node to generate the...

Leaving open, v1 gets some XML love.

Can you give an example or two of the templates you've tried? Does this not work? ``` ruby child :comments do attributes :id, :title end # or even child :comments...

Yeah, what you want is child_root's to be excluded. The use of `include_xml_root` is for the top level root (afaik). This is currently being discussed here in Issue #178 We...

Yeah, I think caching had to be decided on (probably as an option on the collection/object method) but it was close. You knocked most of it out quickly.

I saw @nesquena just merged in the config.include_child_root as an option. Try that out in v0.6.13.

Maybe we can tackle [Issue 119](https://github.com/nesquena/rabl/pull/119) as well by not having to specify: ``` ruby collection @posts => :posts do |p| # ... end ``` and instead allow ``` ruby...

Can I close Pull #178 as well? Anything we need to mention here to make sure that happens as well? (I don't like seeing projects with lots of open issues...

I think bringing several changes into a 1.0 milestone makes the most sense. That way anyone with forks or hacks can address those once throughout all their templates vs piecemeal...

Yeah, most likely the need to add other nodes would force create that root node. Instead of a default collection key, it could revert back to using `posts`. The logic...