timestored / pulseui

Real-time interactive database applications
https://www.timestored.com/pulse/
Other
54 stars 6 forks source link

table click = only some {{e.columns}} #255

Open ryanhamilton opened 2 weeks ago

ryanhamilton commented 2 weeks ago

user-ar user -sid

ryanhamilton commented 3 days ago

user-ab

When an interactive table is clicked, the variables in memory populate inconsistently with each click; some clicks in the table will result in extra fields from the table being held as variables in memory, while clicks on different rows in the same column on the table will not have those extra variables stored. E.g. when I click on row 1 in table X, X.FieldA will be populated and visible in the debug panel, but when I click on row 2, X.FieldA will disappear from the debug panel and any downstream queries will use the stale value of X.FieldA in row 1. This makes the table interactivity feature unreliable to base drilldowns and other user features on. Could this please be fixed? In general, it would be good if there were more optionality on the fields/variables that can be populated in memory given a table click, instead of just the first few fields.