Context Navigation

Changes between Initial Version and Version 1 of Ticket #58962, comment 45

initial	v1
1		@joemcgill I like the plan you've outlined. I agree part of this being more in a rush than usual is because we're so close to the stable release. Given that, I think it makes sense to not tie ourselves to that rush and instead address this holistically in 6.5, for all of the functions being discussed. Any such late release cycle changes put additional stress on contributors and potentially confusion on developers alike for those that may have already read the dev notes.
	1	@joemcgill I like the plan you've outlined. I agree part of this being more in a rush than usual is because we're so close to the stable release. Given that, I think it makes sense to not tie ourselves to that rush and instead address this holistically in 6.5, for all of the functions being discussed. Any such late release cycle changes put additional stress on contributors and potentially confusion on external developers alike for those that may have already read the dev notes.
2	2
3	3	I am all for consistency and I would love for us to revisit the naming of all of these functions in a separate ticket. Whether we rename all of them to `wp_load_()` or `wp_prime__caches()` or something completely different, any such decisions could be made there. Even the functions introduced here could be deprecated again if needed due to a renaming. Granted, it wouldn't feel great deprecating a function introduced 1-2 cycles before, but it's certainly not a blocker and has happened before in core.