Joel Drapper

I’d rather not use different keywords for all these different types of property. @hangsu, I love the suggestion to pass `:positional` in the same place that you’d pass `:&`, etc.

I’m struggling to find a nice way to present all the information. When we have a type failure, we’ll have three things: 1. The type it was expected to be...

> Looking forward to 1.0! We're still pinned to 455f225574dbcb39b7e325a9f75c928a79ec812b and are eager to upgrade/simplify. We’re really close now.

Here’s where I’m at so far. 

Made some progress on this in #98, but we can go further. Specifically, I would like to make collection types recursively add further context, so you know which specific key...

I don’t expect to ship any significant changes to main. I think this is the last bit.

A SyntaxTree mutation visitor would probably be the easiest solution for this.

I agree. I think you’ll find it's easier to use Nokogiri than SyntaxTree for this kind of thing @jaredcwhite. If PhlexML is the final target, you can always do the...

This might be unnecessary since we’ll get a helpful `NoMethodError` anyway when calling `method?` anyway.

You can't use unsafe raw around an attribute, you would need to write the whole element by hand.