global-state inside expression

[jatech1]

Hopefully a simple question... I am playing with the new global-state features in the style. I have it working when using it directly with a property:

"state": {
"stateVarName": {"default": "#00FF00FF"}
}

"line-color": ["global-state", "stateVarName"] // Works fine

But, can't figure out how to use it inside another expression:

"line-color": [
"match",
["get", "id"],
"T",
"rgba(0,0,0,1)",
["global-state", "stateVarName"] // Does not work; always returns null
]

Hopefully I am missing something simple? Any help would be appreciated!

[hiddewie]

This sounds like issue #6048

[jatech1]

Ahh yes it does... thanks. Looks like you said this works: "Using global-state within expressions using simple let and var works"... can you elaborate on this? Did let/var make this work even with "get" in expression or still only without "get"? I am wondering if it is temp work around for my situation above. Thanks!

[hiddewie]

It is not a workaround, because only simple expressions work. Adding ['get', ...] still breaks.

Something like

['let',
  'bearing', ['global-state', 'bearing'],
  'azimuth', 0, // ['get', 'azimuth'],
  ['case',
    ['any',
      ['<=', ['%', ['+', ['var', 'azimuth'], ['var', 'bearing'], 360.0], 360.0], 0 + 60],
      ['>=', ['%', ['+', ['var', 'azimuth'], ['var', 'bearing'], 360.0], 360.0], 360 - 60],
    ], 1.0,
    0.3,
  ],
],

works, but if you add in the ['get', 'azimuth'], again, it breaks (['global-state', 'bearing'] is null)

[Hooterr]

Quick question, does global state work only in paint properties? I'm trying to use it in layout property of symbol layer with icon-size but it always evaluates to null (there's no get expression just 'icon-size': ['global-state', '...'],. That's in the latest 5.7.0.

[HarelM]

In a version that was released a few days ago there were some fixes related to global state, can you check if it helped?

[Hooterr]

I just edited the commnet. I refered to line-width instead of icon-size by mistake. Line width works correctly, icon-size is the one that evaluates to null.

I'm using 5.7.0.

[HarelM]

I would suggest to either try and comment on the relevant PR or open an issue and tag the people who worked on the global-state PRs in recent versions to see if they are familiar with the problem (this is the preferred approach if you'd ask me).
Generally speaking, it is best to provide a minimal reproduction of the issue.