UX Feedback (Operator Descriptions)

[Neilk1021]

Currently a lot of the operators suffer form "if you know, you know" syndrome. While it may be hard to rewrite descriptions for 150 operators, it might be worthwhile to improve a few of the most used ones.

A lot of operators might feel self explanatory, but many obfuscate needed details about how they work, which may lead to user frustration. Take for example the Text Input source. It output's text, sure, but the mechanism for how it does that and what exactly it returns is completely obfuscated. Now as developer we might have the instinct that this is where docs or tutorial videos comes in, but Texera is a User facing product and having to go outside of Texera ruins the workflow.

I don't want to hammer in the sins of this operator too hard, as it's mainly to illustrate a broader point. I think a lot of operators currently fall into this trap and I want to go through to improve their descriptions a bit. A good example of an operator implemented well is the various hugging face operators as a lot of their functionality is self documenting.

In terms of actual questions, I'd like to know what operators developers don't currently know how to use, or operators they remember being hard to use at first.