Don't validate streamed responses

[cshorler]

prior to validation get_connexion_response ultimately calls response.get_data()

I haven't found a workaround for this and the old PR was closed due to inactivity.

I changed it to use getattr as the object may not be a response (could be tuple).

Fixes #904 .

there are also a few other issues raised.

Changes proposed in this pull request:

• bypass for response.is_streamed, otherwise no change in behaviour

[coveralls]

Coverage increased (+0.001%) to 96.294% when pulling e00e609 on cshorler:fix_streamed_response_validation into bed4b95 on zalando:master.

[RobbeSneyders]

Hi @cshorler, thx for the PR. Hopefully you're still interested in merging this :)

In the perfect case, we might want to try to validate the response in a streaming fashion, but this already looks like an improvement. I see two downside as well though:

• Response headers are also not validated anymore
• Users might not expect that validation is deactivated on streaming responses

I think we can address this by logging a warning about this when we skip validation.

Also, we moved to the main branch, so can you please rebase and change the target of your PR?

[RobbeSneyders]

Also, since is_streamed is Flask / werkzeug specific, we should add this as a property to the ConnexionResponse class instead of accessing it directly.

[RobbeSneyders]

Fixes #401 as well

[coveralls]

Pull Request Test Coverage Report for Build 1820352240

• 4 of 4 (100.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.003%) to 97.064%

---

Totals
Change from base Build 1819970533:	0.003%
Covered Lines:	2843
Relevant Lines:	2929

---

💛 - Coveralls

[Ruwann]

Thanks!

This is currently only for flask. For aiohttp, we might need to check what the response class is (https://docs.aiohttp.org/en/stable/web_reference.html#response-classes) but I'm not that familiar with aiohttp myself