feat: custom Spectral rule to ensure content objects contain schema

[barrett-schonefeld]

Purpose:

• Establish a pattern in the validator for adding custom spectral rules and custom spectral functions
• Ensure content objects contain a schema

Changes:

• Add custom spectral rule to ensure that content objects contain a schema
• Add directory to store custom spectral rules and functions
• Add code to retrieve and merge custom spectral rules

Tests:

• Add tests for each use case outlined in the spectral rule

[mkistler]

This does seem to satisfy the requirement but I think it can be simplified while still achieving the same result.

[dpopp07]

I think this looks good but I did have one question about the Spectral implementation to check on before merging (might want to wait for other reviews as well)

[mkistler]

The code here looks good but another key part of creating our own custom rules is documenting them. We probably need to add a new section to the README that describes each custom rule, like the docs/reference/openapi-rules.md in Spectral.

[barrett-schonefeld]

The code here looks good but another key part of creating our own custom rules is documenting them. We probably need to add a new section to the README that describes each custom rule, like the docs/reference/openapi-rules.md in Spectral.

To keep the README.md from getting overcrowded with rule descriptions, I documented the rule in docs/spectral-rules.md and linked to the rule descriptions in the README.MD.

[mkistler]

Almost done, but we need to document this from the point of view of the user.

[mkistler]

Looks good. 👍

[dpopp07]

🎉 This PR is included in version 0.37.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀