fix(spec): restore validation checks in api spec - #123
Merged
Conversation
Kody Review CompleteGreat news! 🎉 Keep up the excellent work! 🚀 Kody Guide: Usage and ConfigurationInteracting with Kody
Current Kody ConfigurationReview OptionsThe following review options are enabled or disabled:
|
Code Coverage ReportTotal Coverage: 13.5% Generated from commit: 3371b40 |
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
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.
The portal IPFS plugin API is again serving the
ValidationCheckschema with per-domain and per-website validationchecks. Syncsswagger.yamlwith the running service, regenerates the client, and re-exportsValidationCheckunder the websites type aliases so bothDomainResponse.ChecksandWebsiteValidateResponse.Checksare usable from the package surface.This pull request restores validation check details in the API specification and generated client. The changes introduce a new
ValidationCheckmodel and add achecksfield to theDomainResponseandWebsiteValidateResponseschemas, allowing clients to receive per-check validation results (including name, status, and details like expected/found values) alongside existing domain and website validation responses. The generated Go client and exported type aliases have been updated accordingly.