Context Navigation

Changes between Initial Version and Version 1 of Ticket #64345, comment 5

initial	v1
11	11	(My assumption is this sort of request comes from folks thinking about Abilities API from the perspective of REST. But the correct mental model should actually be Action/Filter hooks. I think we can agree that `add_filter( 'my_plugin/v2/my_hook' )` is bad dx)
12	12
13		My recommendation is to close this as `wontfix`, and instead focus our efforts on self discoverable ability deprecation, which is what consumers actually need to be aware of. (As mentioned elsewhere, I believe a `deprecation_reason: string\|callable():string\|null` added to input/output fields a la WPGraphQL is the ideal approach).
	13	My recommendation is to close this as `wontfix`, and instead focus our efforts on self discoverable ability deprecation, which is what consumers actually need to be aware of. (As mentioned elsewhere e.g. #64209, I believe a `deprecation_reason: string\|callable():string\|null` added to input/output fields a la WPGraphQL is the ideal approach).
14	14
15	15