When I first started to use context variables, I was only saving primitives and so to change them I had sequences like this: flow.set("stored number",1) //other code temp = flow.get("stored number") temp = temp + 1 flow.set("stored number",temp) This would cause the flow variable "stored number" t…

Probably it is safer to add the final flow.set anyway. As you probably know there are mutating x non-mutating methods array methods. You may get confused if using non-mutating methods, like below: flow.set("storedarray",["1","2"]); //other code temp = flow.get("storedarray"); node.warn(temp.concat…

Also if you decide at some point to use non-memory based context then the lack of the final set, may also come back to bite you..

Thanks for providing the additional reason to intentionally save back to the context variable. I hadn't investigated it, but it is good to know that non-memory (disk) based context works differently relative to assignments to other variables.

non-memory will also include database, cloud, network, and well as disk - ie anything that won't just accept a pointer reference...

Bad form probably, but is this true about context variables

General

tmichaeltx 26 June 2020 13:00 4

This was very valuable to me as it showed how truly complex this area is. In particular, I got a lot of insight out of the youtube video you linked to in that other thread. I am quoting your message in that thread to help others come across it:

Topic		Replies	Views
Unexpected Behavior With Context v19.2 General	1	422	27 November 2019
Unexpected behavior when storing an array in a flow context variable General	4	1092	19 September 2020
Context updated automatically? General	5	231	20 February 2023
Storing data in flow without using flow.set (array of objects) General	6	2252	8 October 2019
Global Context being updated when no global.set executed General function-node	17	695	2 December 2022

Bad form probably, but is this true about context variables

Related topics