Support for non-JSON response validation

[mt-kelvintaywl]

I have an OpenAPI 3 spec that for one of the responses return a HTTP 302 response, for example:

# snippet
paths:
    /faq/{id}:
    get:
      description: |
        fetch a FAQ page (HTTP 302 redirect to our external CMS for FAQ page)
      responses:
        '302':
          description: Response of a Connect redirect
          headers:
            Location:
              schema:
                type: string
               description: Redirection URL
           content:
             text/plain:
               schema:
                 type: string

and since OpenAPI3's response_validate handler will attempt to always parse response body to JSON:

committee/lib/committee/schema_validator/open_api_3.rb

Lines 28 to 39 in fe8570a

	def response_validate(status, headers, response, test_method = false)
	full_body = +""
	response.each do |chunk|
	full_body << chunk
	end
	data = full_body.empty? ? {} : JSON.parse(full_body)
	strict = test_method
	Committee::SchemaValidator::OpenAPI3::ResponseValidator.
	new(@operation_object, validator_option).
	call(status, headers, data, strict)
	end

This is the same for HyperSchema too:

committee/lib/committee/schema_validator/hyper_schema.rb

Lines 31 to 40 in fe8570a

	def response_validate(status, headers, response, _test_method = false)
	return unless link_exist?
	full_body = +""
	response.each do |chunk|
	full_body << chunk
	end
	data = full_body.empty? ? {} : JSON.parse(full_body)
	Committee::SchemaValidator::HyperSchema::ResponseValidator.new(link, validate_success_only: validator_option.validate_success_only).call(status, headers, data)
	end

I ended up having to set validate_success_only to true, but that meant I turned off validation for all non HTTP 2XX responses including client errors (HTTP 4XX) :(

Would be nice for the response_validate to attempt to only parse as JSON based on the Content-Type response header?

[mt-kelvintaywl]

closing this since this is resolved by #273