Context Navigation

Changes between Initial Version and Version 1 of Ticket #64505, comment 9

initial	v1
15	15	Thank you for bringing up this issue, it has highlighted to me that we should go back and make these parser classes more scary, private, and possibly even `@ignore` to strip them out of the documentation. They should probably also be final, and have scarier names, but they were never meant to see the light of day so the name was perhaps a little more relaxed than it should have been.
16	16
17		You all are wonderful; and really it’s great to embrace standard types with built-in documentation. In this particular case though I think it is a ticking time bomb to use //this particular class/. I can propose a `WP_Block_Node` class before the week’s end if you would like that.
	17	You all are wonderful; and really it’s great to embrace standard types with built-in documentation. In this particular case though I think it is a ticking time bomb to use //this particular class//. I can propose a `WP_Block_Node` class before the week’s end if you would like that.