Hey guys,
I've ran into this problem before and it took me a while to figure out the issue. I've ran into it again while just playing around with a small app.
In the 'exclude' attribute, they show the leading comma. In the 'fields' attribute, they don't. I haven't ran their exact example -- but something very similar and I get a weird error, unless I throw in the trailing comma after the final element of the tuple.
I'm just wondering if anyone can verify that this is a bug with the documentation before I start the journey of searching through the existing tickets and filing one if it hasn't been reported.
Thanks!