ota42y
ota42y
I fixed rubocop warning and these test failed occurred in develop branch so I think this change is no problem.
Sorry, we are not currently implementing it, and we have no plans to do so for the time being.
At the moment there are none. However, if there is an error, we would like to have some workaround (no verification, but no error either).
https://github.com/ota42y/openapi_parser/pull/51/files#diff-b88c8907571865f9d8cbdcb0a78c051eR71 This change use `match?` method, it not support ruby 2.3 (ruby 2.4 or later) But we can use other way to support ruby 2.3 so we dosen't drop support....
Yes, we should be fix this problem! This is bug because we check UUID format and this string pass checking :thinking: https://github.com/ota42y/openapi_parser/blob/master/lib/openapi_parser/schema_validator/string_validator.rb#L69
Thank you your contribution!!!! I reply your PR 😄 I think it's a very good first step!!
- This gem raise error when validation is failed. - This gem return `nil` when validation passed. - In this case, we can't find media type object so don't validate...
Late reply, but I got back to you, thanks for pointing it out right!
I think we should create new option like `header_coerce`
There is no reason to rush to release a new version, so give it a try! 😄