encode
Prevent head method mapping to coerce action name
This PR resolves an untested backwards incompatible schema change that sneaked in along with the 3.12 release.
In the nested view of ViewSetMixin, the head method is auto mapped here to the get action, leading to the view's action mapping to contain more than 1 mapping under normal read conditions.
The length of the action map is later used to determine the action names and depth for the links in the schema document, generated by SchemaGenerator.
The head method should not be accounted for when generating the depth and details of the links, since it's not part of the schema anyways.
Furthermore this also propagates and changes the operation ids for the affected actions.
Friendly ping @carltongibson. Is it possible to get this patch merged?
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.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
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.
