Skip to content

Always check a schema has a type when returning errors.#18

Merged
daveshanley merged 1 commit into
mainfrom
v0.0.12
Aug 7, 2023
Merged

Always check a schema has a type when returning errors.#18
daveshanley merged 1 commit into
mainfrom
v0.0.12

Conversation

@daveshanley
Copy link
Copy Markdown
Member

As reported in #16, types may not always exist (so the schema is completely invalid anyway). However, it’s essential to make sure that we check for the type before using it.

As reported in #16, types may not always exist (so the schema is completely invalid anyway). However, it’s important to make sure that we check for the type, before using it.

Signed-off-by: Dave Shanley <dave@quobix.com>
@codecov-commenter
Copy link
Copy Markdown

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (dca35f7) 100.00% compared to head (2ef2a2e) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #18   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           18        18           
  Lines         1011      1021   +10     
=========================================
+ Hits          1011      1021   +10     
Flag Coverage Δ
unittests 100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed Coverage Δ
requests/validate_request.go 100.00% <100.00%> (ø)
responses/validate_response.go 100.00% <100.00%> (ø)
schema_validation/validate_schema.go 100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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.

2 participants