You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While exploring app.py and conf.py, I observed that even if I pass a different port or api-name inconf.py it still listen to base-url & api-name provided while making documentation using doc.writer.HydraDoc(). It can be verified in the below image:
Api-name in the hydra_doc_sample.py (reference image attached below) is api but in conf.py I passed it as testapi . When I fire a request on /api then it gives me 200 but for /testapi it throws 404.
Snap of hydra_doc_sample.py :
Snap of myconf.py :
Expected Behaviour:
The server should listen to http://localhost:8080/testapi rather than http://localhost:8080/api
Steps to reproduce:
change API_NAME in conf.py from to api to testapi
run app.py and fire request on http://localhost:8080/testapi
Environment:
python version - 3.8.0
pip version - 22.0.2
OS details
Name - Microsoft Windows 11 Home Single Language
Version - 10.0.22000 N/A Build 22000
Do you want to work on this issue?
Yes
The text was updated successfully, but these errors were encountered:
I'm submitting a
Current Behaviour:
While exploring app.py and conf.py, I observed that even if I pass a different
port
orapi-name
inconf.py
it still listen tobase-url & api-name
provided while making documentation usingdoc.writer.HydraDoc()
. It can be verified in the below image:Api-name in the hydra_doc_sample.py (reference image attached below) is
api
but inconf.py
I passed it astestapi
. When I fire a request on/api
then it gives me200
but for/testapi
it throws404
.Snap of
hydra_doc_sample.py
:Snap of my
conf.py
:Expected Behaviour:
The server should listen to
http://localhost:8080/testapi
rather thanhttp://localhost:8080/api
Steps to reproduce:
API_NAME
inconf.py
from toapi
totestapi
app.py
and fire request onhttp://localhost:8080/testapi
Environment:
Do you want to work on this issue?
Yes
The text was updated successfully, but these errors were encountered: