Should the Select node allow invalid input?

In this simplified example:

The select node will always pick A. Yet it is giving the warning “accessed none” from the Empty Char Ref. But if it’s picking A, why does it matter if B is invalid?

The reason I want invalid input is because I’m doing some simple AI. If it has a valid target, select the option with the valid target. If it does not, select the other option. So now I instead have to create more functions, or queries. But it would be so handy to just have this one select node.

I can’t tell if this is a bug/oversight or if it is intended. What do you think would be the better option?

Maybe the “IsValid?” action can do the sorting? It will check if the input object (Empty Char Ref) is valid and branch based on the result.

I think it’s what you’re looking for, but not sure.

I appreciate you’re trying to help, but I know how to query if it’s a valid option. But that leads to either multiple functions for the action I’m doing, or creating more variables to store the valid result to use for the function.

It’s more a quality of life question about the practicality of allowing invalid input into the select node, so you wouldn’t have to do the above.

Some example setups.