-
Notifications
You must be signed in to change notification settings - Fork 23
related_field not recognised in URL path #286
Comments
This is the relevant code tasked with resolving paths: https://github.com/snok/drf-openapi-tester/blob/master/openapi_tester/loaders.py#L141 My guess is that the answer will be found there if you take a look. A PR with a fix is, as always, welcome 🙂 I could also take a look at this at some point, but would need reproducible code in some form or another |
Thanks for your reply. I will try to push reproducible code as you have described here |
I was able to reproduce this locally, however when I push to the PR it fails. Seems it cannot import Could you please have a look and assist me in how to get this operational. Thanks |
I'll try to take a look at both issues tomorrow 👍 |
@sondrelg Did you get the opportunity to look into this issue, from the reproducing PR? |
Hi @darduf, thanks for pushing the reproducible code. That's helpful. Unfortunately, I do not have time to look at this in the near future, so I would suggest looking at it yourself if you need this fixed. I'm happy to answer questions and guide you if there's anything you need. Just let me know 👍 |
We are using RelationshipView from the DRF JSON:API package, and are experiencing limitations when using the schema tester on these type of endpoints.
We have the following path/view that handles the application of team members (POST/DELETE)
When
SchemaTester(schema_file_path=path/to/schemae/file.yaml)
hits this pathWe receive an
UndocumentedSchemaSectionError
Why isn't the (undocumented) path resolving
/api/team/{id}/relationships/{related_field}
to the (documented) desired path/api/team/{id}/relationships/members
as expected?Is there something additional that needs to be defined in order for the schema tester to recognise these
related_field
path keys?The text was updated successfully, but these errors were encountered: