Flattening of nested models is really confusing in APIView for Swaggers

[heaths]

Based on the swagger, only a ResolvedConstentList is returned, but this "flattening" of models makes it seem like either could be returned:

See APIView for more examples.

I would just show the response model (if any) and make sure the properties are linked to the definitions.

[mikekistler]

This will be a change in the parser. Should not be too hard but we need to investigate.

[heaths]

Given the request to link models anyway (from elsewhere - not just me), seems that part should come for "free". Just need to stop unrolling the nested models into this location such that, for example, only ResolvedConsentList is documented and its value field (rather, the Type/format column) links to ResolvedConsent.

[heaths]

In the interim, how hard would it be to link to the original swagger - whether in a PR or whatever the originating branch is from? Often times I feel confused by APIView (like this as a prime example) and need to double check with the swagger.

[maririos]

In the interim, how hard would it be to link to the original swagger - whether in a PR or whatever the originating branch is from? Often times I feel confused by APIView (like this as a prime example) and need to double check with the swagger.

You mean to correlate a specific teable/view with the respective line in Swagger?
or is the Associated Pull Request view enough

[heaths]

The PR is sufficient, since I can still view the individual swagger that way: either the diff, or click "View file" on the web to view the whole file. Thank you. I had not noticed that. I typically collapse options.