feature/json-validation

[BrianL3]

Link to Relevant Issue

This pull request resolves #150

Description of Changes

As part of ModelService's sanity checks (did anything get returned from NetworkService? was there an error? etc) before it creates a Model, it now checks to see if the required properties are on the json. This does not cascade down, but we have very flat database objects so it works out.

This enables us to have required properties on our Model objects.

Link to Forked Storybook Site

Storybook (no changes to visual components)

[tohuynh]

Have some fixes for reqruied fields and TransriptJson.

And a general question regarding the creation of new Model out of a model_ref pattern:

if (typeof jsonData["body_ref"] === "object") {
      this.body = new Body(jsonData["body_ref"]);

To pass the two test cases, add the required fields for the example Event at
https://github.com/BrianL3/cdp-frontend/blob/feature/json-validation/src/networking/test/ModelService.test.ts#L10
https://github.com/BrianL3/cdp-frontend/blob/feature/json-validation/src/networking/test/ModelService.test.ts#L18

Promise.resolve(new NetworkResponse({ agenda_uri: "test", <add required fields> }))

[tohuynh]

getRequiredProperties also need to be updated after changing the model files to have missing required fields as well.

[evamaxfield]

This all looks good to me. Once again, I cannot wait until we get a backend person / a dev ops person to write some fancy code gen for this type of stuff.