Numeric operators not searchable by the operator and have no display ports

[radeusgd]

2 (possibly related) issues with numeric operators:

When I have a number node and press tab, I want to create an operation on numbers.

1. When I type / to create a 'division' the searcher does not show a / operator - which is there.

Interestingly, if I search by the Alias - start typing divide, it will show up:

However, after selecting that method from CB and creating a new node, the node does not show an input port for the second number argument:

I would expect an input port on the right-hand-side of the / operator here.

The same happens for other kinds of operators:

As a side note, if I want to search by name, the - can be found by typing Subtract. However, typing Minus does not find it. IMO it should also be searchable by minus.

[kazcw]

Fixing the missing ports is blocked on backend support: #6374

[farmaazon]

When I type / to create a 'division' the searcher does not show a / operator - which is there.

It not literally true, as the operator is there: it's just on the top of Base.Data section. We just do not filter by / and there is a reason for that:

If one write + or \, they already typed their operation and want to add operands now. Thus, it felt sensible to show all suggestions to pick potential operand instead displaying suggestion of operator which in 99% is already complete at this point.

Now, the only sensible improvement I can think of is treating spaces as parts of the operator; so if the user types 2 + without a trailing space, we can assume we're still typing the operator. The question is how often user would prefer to make "partially applied operations", like foo +2.

[farmaazon]

Copied from #7105 a comment by @wdanilo :

If the user types <, the Component Browser should indeed hint something starting or containing <. No reaction from Component Browser is indeed a bad behavior. Just a small explanation.

@wdanilo could you somehow refer to my doubts in the comment above? And how it would work when user types 2+ (without any spaces)? I think they could expect suggestions for second operand (what's the point of displaying a single suggestion for + at this point)?

[jdunkerley]

Still an issue with newest CB - we should be able to find operators when typing.