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
I'm on a recent snapshot (4038) and I've stumbled across a very strange bug. If the array methods available in the expression parser are applied to a repeater's loop source array in an expression, the UI completely freezes.
Here's what I mean. Let's start with a simple demo widget that works just fine:
Chaining works just fine too, you can easily tack a .reverse() on to either of those expressions with no ill effects. So, the array methods themselves are quite functional.
Now here's where it gets weird:
If you replace the array in the after expression with loop.test_source (which should be identical), the entire page becomes fully unresponive and must be externally killed.
Even stranger, it's only in the child components! You can apply methods to the source array in the repeater's map property. This will correctly sort the output of the repeater:
This can be replicated in Chrome and Firefox. I also went back and checked a couple older images I still had lying around so I can confirm it goes back at least as far as 4.1M4. I honestly can't say that I remember with 100% certainty that this ever worked in the past, so I don't know whether this is some regression or has always been inherent to the repeater.
The text was updated successfully, but these errors were encountered:
I'm on a recent snapshot (4038) and I've stumbled across a very strange bug. If the array methods available in the expression parser are applied to a repeater's loop source array in an expression, the UI completely freezes.
Here's what I mean. Let's start with a simple demo widget that works just fine:
This functions as expected. You can even use specialized sort functions:
Chaining works just fine too, you can easily tack a
.reverse()
on to either of those expressions with no ill effects. So, the array methods themselves are quite functional.If we move to a repeater:
This gets the expected output:
Now here's where it gets weird:
If you replace the array in the after expression with
loop.test_source
(which should be identical), the entire page becomes fully unresponive and must be externally killed.Even stranger, it's only in the child components! You can apply methods to the source array in the repeater's
map
property. This will correctly sort the output of the repeater:This can be replicated in Chrome and Firefox. I also went back and checked a couple older images I still had lying around so I can confirm it goes back at least as far as 4.1M4. I honestly can't say that I remember with 100% certainty that this ever worked in the past, so I don't know whether this is some regression or has always been inherent to the repeater.
The text was updated successfully, but these errors were encountered: