I'm thinking about the status topic - the text property remains the current status under the node and a new property description allows to show more in the Sidebar.
There are already three and I don't see what you want to do with the new one? Highlighted the description?
There are other (contributed) nodes that would potentially benefit from such a split and I'm hoping that when Node.js v20 (or might be 21, can't remember) becomes the baseline with full support for submodules, this will be more straightforward because you will be able to use a monorepo "properly". Well that's my understanding anyway.
In my defense, I would like to say that I posted this feature request out of a certain frustration, after spending at least an hour trying to reinvent the wheel, only to realize shortly thereafter that I had neatly documented everything in the (hidden) node's description some time ago.
Nobody likes overcluttered GUIs. So maybe, it is indeed a bad idea to implement this.
I don't think it is a bad idea, but maybe not something that everyone wants on all the time.
Just trying to play with some ideas myself as, even if this isn't adopted in core, I think I'd like something I could implement myself (and share with others of course).
But at the moment, I'm slightly struggling to adapt @gregorius's code above:
His current code only updates after you open and close a node. Is there an event that I could use that will trigger when the page is loaded and after all the nodes are rendered?
Positioning not yet allowing for different node sizes but starting to get there:
Personally, I think that some kind of icon, even an i would be distracting, especially if you have a lot of descriptions.
As others have commented I think, it is really very easy to ruin a visual UX with clutter.
But just my opinion.
More importantly though, getting to a consistent bottom-right is actually quite hard unless you amend core I think. Since nodes can change size. Though haven't tried that hard so I may be missing something obvious.
Of course, none of this is accessible. But accessible visual programming is a very hard problem. And since the description can still be accessed other ways, there probably isn't an easy answer.
I understand Remo's frustration, what he is asking is to just know that a node has a description - like the "inject" node does when enabling the repeat.
This is precisely the kind of idea that Nick and Dave try to avoid because it pollutes the rendering of the node. It shouldn't be too visible and the idea of a new badge is disturbing (and too showy)
I had this kind of idea, initially I wanted something that looked like the "file-text" icon but I couldn't get the right size (because svg). To see if the upper corner is better