Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: support to validate the response via JSON schema #38

Merged
merged 1 commit into from
Apr 12, 2023

Conversation

LinuxSuRen
Copy link
Owner

No description provided.

@LinuxSuRen LinuxSuRen force-pushed the feat/json-schema-validate branch from 7aba620 to cc6ba7e Compare April 12, 2023 04:26
@codacy-production
Copy link

codacy-production bot commented Apr 12, 2023

Coverage summary from Codacy

Merging #38 (9b52704) into master (2f93d1d) - See PR on Codacy

Coverage variation Diff coverage
+0.20% 100.00%
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (2f93d1d) 901 772 85.68%
Head commit (9b52704) 914 (+13) 785 (+13) 85.89% (+0.20%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#38) 13 13 100.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

@LinuxSuRen LinuxSuRen force-pushed the feat/json-schema-validate branch from cc6ba7e to 9b52704 Compare April 12, 2023 04:41
@LinuxSuRen LinuxSuRen merged commit 9ee38ff into master Apr 12, 2023
@LinuxSuRen LinuxSuRen deleted the feat/json-schema-validate branch April 12, 2023 05:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant