Address Speccy and Spectral linting errors and warnings #313
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There were a number of Speccy and Spectral errors and warnings that are worth looking into now that Spectral is running again.
In this pull request I've addressed some of these:
There are still errors about
"type" property must be equal to one of the allowed values: "array", "boolean", "integer", "number", "object", "string".
in a number of collection files. This seems to be spurious, and indeed when I reproduce this by running Spectral locally in the VS Code extension, when it hits one of these Spectral stops with an error and directs me to look at its output. The actual JSON Schema looks correct - there is an array, and the error occurs at the start of the "items" clause, not in the "type" clause. It doesn't even work if items is a simple type.