You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of exposing it is a a cursor, we could expose results from an query as an array which gets updated using its native methods (which Vue overrides). This might be better than current approach where we expose it as a cursor and patch Vue to support iteration over it. Not sure though how much does Vue do with patching native methods: do they just trigger reactive invalidation or does it also take into the account what exactly changed in an array and optimize based on that?
Instead of exposing it is a a cursor, we could expose results from an query as an array which gets updated using its native methods (which Vue overrides). This might be better than current approach where we expose it as a cursor and patch Vue to support iteration over it. Not sure though how much does Vue do with patching native methods: do they just trigger reactive invalidation or does it also take into the account what exactly changed in an array and optimize based on that?
Code here is doing such changes.
The text was updated successfully, but these errors were encountered: