Open filipealc opened 4 years ago
hi, all. how to fixed it?I already get this problem
I'm seeing this as well, and my project relies heavily on nested validation. My example is pretty similar to the OP but I have a production endpoint using Nested and I get this trace in postman and in integration tests.
EDIT: For reference I'm running restx 0.3.0
alembic==1.5.8
AMQPStorm==2.8.4
aniso8601==9.0.1
attrs==20.3.0
certifi==2020.12.5
cffi==1.14.5
chardet==4.0.0
click==7.1.2
coverage==5.5
cryptography==3.4.7
decorator==5.0.7
directly==0.0.30
Flask==1.1.2
Flask-Cors==3.0.10
flask-restx==0.3.0
flask-talisman==0.7.0
greenlet==1.0.0
idna==2.10
iso8601==0.1.14
itsdangerous==1.1.0
Jinja2==2.11.3
jsonpath-ng==1.5.2
jsonschema==3.2.0
Mako==1.1.4
MarkupSafe==1.1.1
mysqlclient==2.0.3
pamqp==2.3.0
ply==3.11
psutil==5.8.0
pycparser==2.20
pycrypto==2.6.1
PyJWT==1.7.1
pyrsistent==0.17.3
python-dateutil==2.8.1
python-editor==1.0.4
pytz==2021.1
regex==2021.4.4
requests==2.25.1
six==1.15.0
SQLAlchemy==1.4.8
urllib3==1.26.4
Werkzeug==0.16.1
I came across this issue while I was editing a model and started using a Nested
field. When running my tests, I got the error referenced in the issue:
"Unresolvable JSON pointer: %r" % fragment
jsonschema.exceptions.RefResolutionError: Unresolvable JSON pointer: 'definitions/test_case_params'
Having a look to the error message and to the endpoints, I realised that the endpoint was defined with doc=False
, so I guessed that no schema was being generated. After removing doc=False
from the endpoint, the errors disappeared and validations started to work.
I know it's not the same use case as in the original issue, but it may help someone in the future. Tested in flask-restx 0.4.0
I have been running into the same problem. If anyone has a solution it'd be much appreciated
I have been running into the same problem. If anyone has a solution it'd be much appreciated
Just realised people are remaking the whole marshalling.
Same problem while parsing open API specification via yaml.loader. Is there any other way to validate nested schemas from open API specification apart from parsing it into json and using json schema validation?
Hello Folks,
When running a test case against an endpoint I'm getting the following error:
Pip freeze:
Full traceback:
The endpoint
The Test Case
Note that before trying to migrate restplus to restX this was working as expected but on restX this error starts to pop up and if I set on the endpoint validate=False the problem would go away! So I think that there's some kind of problem when restX is trying to validate the params