A suggestion, you can also add console.log(“some variable”); to help you debug.
And also take some time to learn Javascript, it’s both super handy and nowadays, you can code everything with it. For example, if you want to code a fullstack JS app with Vue or Next.
Excellent suggestion of MaximeBaker,
In JS, if a data is empty it doesn’t exist. Thus if(!p2) = empty = code will stop.
Again, learn JS guys and girls, it’s top language
Yes, the JavaScript executes client-side (in the browser). This is why we always warn against using JavaScript to make authenticated API calls.
The same is true for the Experimental Code column. Even though you might be hosting the code on GitHub, the code is first loaded onto the client device and then executed locally.
As far as when it is executed, my understanding is that it’s the same as all other computed columns - that is, the JavaScript will execute whenever the column is referenced. Although there might be some local caching involved - I’m not sure about that.
As far as when it is executed, my understanding is that it’s the same as all other computed columns - that is, the JavaScript will execute whenever the column is referenced. Although there might be some local caching involved - I’m not sure about that.
Nope Darren, “experimental” JS column tables are always executed quite fast for me. But maybe because my Glide tables are below <20k records. There is a mix of cache and in RTDB in Glide Tables. Who uses Firestore as a data storage in backend. A very good tech if you ask me.