Remove broken OpenAPI validation #17
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This workflow attempts to validate the openAPI.yaml file, but it never passed, not even at the time it was first added. The configuration it uses for the linter is now outdated - the linter no longer uses .validaterc. Modifying the spec to adhere to what the linter expects would, at this point, involve modifying the interface exposed by other projects, which would be a significant undertaking. Additonally, the API spec hasn't been modified in years, so linting it regularly doesn't seem particularly useful.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This workflow attempts to validate the openAPI.yaml file, but it never passed, not even at the time it was first added.
The configuration it uses for the linter is now outdated - the linter no longer uses .validaterc.
Modifying the spec to adhere to what the linter expects would, at this point, involve modifying the interface exposed by other projects, which would be a significant undertaking (HSDS, h5pyd, possibly others).
Additonally, the API spec hasn't been modified in years, so linting it regularly doesn't seem particularly useful.