Pin jsonschema to v1.2.2

[intelliot]

• Fixes SchemaError: no such schema </tag> #880
• Uses yarn upgrade to update yarn.lock

I believe these are already the dependencies that would be used by ripple-lib consumers, so there's no additional risk/harm in updating yarn.lock here. There's still risk that dependencies could introduce breaking changes at any time; I think we should address this by reducing our number of dependencies and by pinning more dependencies to specific versions (don't use ^ or ~).

[FredKSchott]

very strange. lgtm!

[enVolt]

Hey Guys, any update on this. Currently, ripple-lib is broken because of this.

I think we should address this by reducing our number of dependencies and by pinning more dependencies to specific versions (don't use ^ or ~)

I used to hate Maven for not allowing me to upgrade automatically in case of a patch release. And these kind of issues, puts faith in Java ecosystem.

I earlier faced a similar issue with Mongoose library, and swear to God, I removed all those funny symbols (~ or ^) from all the repos which I had access to in my organization. Unknowingly I was living a better life.

[intelliot]

@enVolt I appreciate that you've let us know that this issue is also affecting you. I'll merge it now and do a release. Thanks!

[intelliot]

The fix is included in 0.20.0. Please create an issue if you still notice any problems. Thank you!

[awwright]

@enVolt @intelliot I'm still waiting on confirmation that using a correct URI fixes the application. Please see tdegrunt/jsonschema#253

[FKSRipple]

Did a little digging here, and found that in the new update schemas seems to have changed from a title->schema structure to a more complex data-structure, with nesting (ex: `'/signParameters#/properties/keypair' is a title in the schemas object with the latest version). This seems to have caused our issue.

[awwright]

@FKSRipple If it's an error related to tdegrunt/jsonschema#253 and you can put together a test case, I'd be happy to consider adding it