Add guards for potentially undefined field

[hanna-greaves]

It is possible that the validations on an entity field can be undefined, leading to type errors. This change adds guards to avoid this situation.

Resolves #18

[marcolink]

@hanna-greaves awesome - thank you so much 🎉

I'm wondering if we should add some tests for it, wdyt?

[hanna-greaves]

Ah yeah probably a good idea! :) I will take a look at adding some asap!

[hanna-greaves]

@marcolink I've added a render test, I'd like to add a definition test as well, but the Definitely Typed definitions need to be updated to make FieldValidations optional, since they're not guaranteed to be defined.

Would you be okay with merging this change and then me creating another PR to add a test for that once I've made an update for the Definitely Typed definition?

[marcolink]

@hanna-greaves looks great, will merge it right away!

[github-actions]

🎉 This PR is included in version 1.2.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[marcolink]

@hanna-greaves and regarding your question about types in need of an update,
What exact package would that be?

[hanna-greaves]

I had thought the types were in definitely typed, but they're coming from the main Contentful package :) I am writing up an issue now if you don't mind me @'ing you on it?

This line specifically is the problem

[marcolink]

Ah, interesting. And yes, feel free to add me :)