Dashboard

I'm not so sure. The best I can find is that for is pretty much always the fastest, and for of only seems to be a slight issue with massive datasets (far beyond what a frontend app would do). And for of is still faster than forEach. 

In any event, forEach still has way too many other limitations, and for of is much more readable than for when you don't know the size of the array you are iterating over. 

See: 

• https://leanylabs.com/blog/js-forEach-map-reduce-vs-for-for_of/#arrayforeach-vs-for-and-forof
• https://blog.bitsrc.io/finding-the-fastest-loop-type-in-javascript-38af16fe7b4f

This only applies to Javascript. I'm not sure how this applies to other languages.

Great tips John!

HaHa, thanks for that, Ron.  I've got so much still to learn.  I'd like to go 'interactive' with my widgets.  I'm hoping to get some insights that don't take me days to figure out.

Thanks for that Ron.

For the benefit of others, remember to use the Overflow text tab to constrain and scroll down a long list of json objects.
Also. to examine a selected table row as json displayed in a text widget, I had to save the selected row
from the table onRowselected option with {{await storeValue('selectedRow', TblAlldocs.selectedRow)}}
and feed the Input widget with {{appsmith.store.selectedRow}} in its text box.

I looked at displaying the json in an Input widget but it would only work as a fixed-size, unscrolable, multi-line text block;
a single-line text Input widget could only display the json as a realistically, unreadable long string. 

Absolutely. If you bind the default query result to something like a Text widget, it is in JSON format already:

{{ Query1.data }}

Just be sure to use .data and not .run() . If you use .run(), then it will actually make the DB query again instead of using the results you already retreived.

This will most likely be out in the latter half of this year!

Lol - nice try Paul. We all know you rock.

Thanks for the feedback, Oscar! I can't take all the credit here, Joseph and the Templates team created the original list internally, and I just posted a modified version after finding it so useful.

The really helpful thing is when you are using autocomplete - you can find widgets/js/queries much easier when they are named properly, AND you know what they are without needing to look them up.