Fix OR expressions with true on the left hand side

[iconara]

This fixes a bug where foo || bar where foo is true fails with NoMethodError: undefined methodempty?' for true:TrueClass`.

[trevorrowe]

Thanks for the pull request and fix. @jamesls What are your feelings about expanding the compliance tests? Should be this included in the default suite, or should these be moved to Ruby implementation specific tests? The root of the issue is how the Ruby implementation used .empty? method in was being invoked to determine falsey-ness.

[trevorrowe]

@jamesls @iconara I just took a look at the jmespath/jmespath.test repository, and there appears to be quite a few new tests. Included is a new suite for dealing with booleans. It looks like the new booleans.json test suite would cover this feature and not require the other test change.

[iconara]

Getting better (and standardized) tests sounds like a great thing. Is there any easy way to link it in so that it will remain up to date?

[jamesls]

@trevorrowe Yep, I believe these should now be accounted for in jmespath.test. There's a recent JEP that improved general boolean support in jmespath (jmespath/jmespath.site#16).

I would like to get a more automated system in place for when new tests are added to jmespath.test to better communicate test suite updates. I tried using submodules for a while in jmespath.py, but that ended up being more trouble than it's worth.

[trevorrowe]

Sorry for the slow response on this. I merged your pull request locally, and then updated the compliance spec tests. I've got a few other things to wrap up and then I'll try to get a new release cut.