Fixed has_shape to handle nested json properly.

[sroymdsol]

For nested shapes the has_shape method was examining only values of the root json object instead of looking at the actual json child element. For example:

json: {"key1": {"key2": "value2"}} shape: {{"key1", Json::Type::OBJECT}, {"key2", Json::Type::STRING}}

In this case has_shape would return false because it would look for "key2" in the root json object instead of under the key1 object.

I added a simple test to verify the behavior of has_shape.

[artwyman]

I agree that the current code doesn't support nested shapes in a single has_shape call. I think that your diff here no longer supports non-nested shapes at all, though (i.e. what if key1 and key2 are supposed to be siblings). I think it would take a more complex recursive implementation to support both at once. I think in our existing use cases we do multiple checks as we process different parts of the input. Check the shape of the top-level object, then extract a sub-object you want, then check its shape.

[sroymdsol]

True true. Tough proposition to model a shape object that can do this. Probably not worth it for my needs. Thanks!