Context Navigation

Changes between Initial Version and Version 1 of Ticket #51525, comment 34

initial	v1
1	1	It came up in the discussion as apparently, a majority of filters in the core could not use a single type. I don't know the Core well enough to have an opinion on that though.
2	2
3		I can see how nullable types could be used, ~~abusing a bit boolean~~ with null cases for instance.
	3	I can see how nullable types could be used, with code abusing a bit booleans and being permissive with null cases for instance.
4	4	About union types, we would probably not use it as plugin or theme developers, because as you mention, it's a bit missing the goal of simplifying safe checks (and that's probably why we did not even think about it in the first place). But if it is not too complex to add and it can help adoption for already existing filters, we would give it a go...