Closed mathgladiator closed 1 year ago
This can be fixed because we can detect when Time is used.
if (resolved instanceof TyNativeGlobalObject) { if( ((TyNativeGlobalObject) resolved).globalName.equals("Time")) { depends.add("__time"); } return; };
this can help fix the issue, but it also introduces noise for pure methods.
if (resolved instanceof TyNativeGlobalObject) {
if( ((TyNativeGlobalObject) resolved).globalName.equals("Time")) {
depends.add("__time");
}
return;
};
Also, this makes me think we need to sort out how fields within a record/message/global contribute to the dependencies of a function. We should test methods on records don't break reactivity in bubbles.
A user that transitions from 11:59PM to 12:00AM will not trigger an update. Similar to Time.datetime() and Time.now();
At core, I need a new subscription base for Time.$X() calls in bubbles/formulas where a meaningful invalidation happens on a schedule.