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
Probably has to do with the fact that the timestamp input param is a moment() object vs ISO string, so rendering gets triggered everytime a new object is sent, and not when the timestamp actually changes.
Making timestamp param a string would probably fix the problem.
The text was updated successfully, but these errors were encountered:
fbarl
added
the
bug
Broken end user or developer functionality; not working as the developers intended it
label
Nov 2, 2017
Probably has to do with the fact that the
timestamp
input param is amoment()
object vs ISO string, so rendering gets triggered everytime a new object is sent, and not when the timestamp actually changes.Making
timestamp
param a string would probably fix the problem.The text was updated successfully, but these errors were encountered: