It's not immediately obvious to mewhen this'd be useful to have as public API, since it only makes sense to use if you've got referencesoutside of the standard'$ref': '#/components/schemas/{...} space.

Are you able to provide some kind of slimmed down example that'd require this as public API?

@tomchristie

Are you able to provide some kind of slimmed down example that'd require this as public API?

I'm extending get_schema() and so far have two remaining private API calls:_get_reference and_initialise_endpoints

https://github.com/django-json-api/django-rest-framework-json-api/blob/c1ceb7f42b98ee382c11372e72933a8fbdfe9691/rest_framework_json_api/schemas/openapi.py#L547-L559

Okay, so... making it public not because you want to override the behaviour in it, but rather, making it public because your implementation needs to call it? That makes sense I guess.

@tomchristie should this be inmilestone 3.13 and/or labeledschema generation?

@carltongibson perhaps you can review this and put it on Tom's queue for 3.13?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This stalebot stuff makes me sad that I wasted effort on submitting PRs.

This seems reasonable enough, yes.