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
Currently calling @beacon_live_data with an invalid key will just return nil since that's a regular map. That's safe but easy to miss and may result on incorrect behavior.
We want to explore ways to make @beacon_live_data behave more like LV @assign and warn and/or fail to compile if such value is not existing.
The text was updated successfully, but these errors were encountered:
My recommendation is to copy all of the keys from @beacon_live_data and whatever keys we want to expose from assign into a new assign variable prior to the template compilation. This way we limit to only what we choose to expose for template rendering. Otherwise someone could do this:
Currently calling
@beacon_live_data
with an invalid key will just returnnil
since that's a regular map. That's safe but easy to miss and may result on incorrect behavior.We want to explore ways to make
@beacon_live_data
behave more like LV@assign
and warn and/or fail to compile if such value is not existing.The text was updated successfully, but these errors were encountered: