Protocol and port control

[vpet98]

Based on issue #176.

I added a parameter in the add_explorer_view, so that it is possible to define the protocol (e.g. https instead of http) in the specification url. In such case, the port of the application also needs to be given in the route_url function of pyramid Request object, that's why the added parameter is a tuple of two values.

[zupo]

Looks good! Can you add a test as well please?

[vpet98]

Thank you! I added a test for this case.

In order to make the test work I had also to add a host parameter in the add_explorer_view function. I am not sure why it would fail without that parameter, maybe it has to do with the DummyRequest object. If there is a way to avoid this, please tell me so that I can omit this redundant code.

Either way, I believe the user doesn't need to specify the host parameter when calling pyramid_openapi3_add_explorer to solve the problem described at issue #176. They only need to specify protocol and port.

[jschaeff]

Hi @zupo, thank you for taking time to review this PR.

Can you tell roughly when it could hit the next release ?

Cheers

[zupo]

I first need to figure out why all tests are failing.

[zupo]

I had to rewrite this PR a bit: #207

[zupo]

In order to make the test work I had also to add a host parameter in the add_explorer_view function. I am not sure why it would fail without that parameter, maybe it has to do with the DummyRequest object. If there is a way to avoid this, please tell me so that I can omit this redundant code.

This problem only seems to affect the tests so, I just fixed the tests instead of adding a new host parameter.