bigopon

@dkent600 it's not biased towards any, it's actually just a "pseudo router" (my name for it), as it's aimed for a very stripped down router + plain templating. This idea...

Hmm, interesting, thanks and sorry for the wait @krisdages this' been missed. I'm not sure if you are still interested, but I'll just comment for anyone who is ```ts //only...

Hmm, this is because when `[...]` stands alone, it's understood as an array, per our expression parser, I think. Likely a workaround will be `$this[...]`, can you try that @ekzobrain...

if we have `['1a']`, it'll be understood as an array in an expression mode, We'll probably need new parsing mode as property access.

Thanks for reporting this @ekzobrain , at the moment, only a text binding automatically observes the array to update, as it's a pretty common thing to throw an array at...

though it should be noted that there's no special "join" function, it will simplify call `String(array)` to get the value, which means `['class-1', 'class-2']` will turn into `class-1,class-2` instead of...

@fkleuver I just realised in our computed observers, we need to tweak the change handling timing as well. At the moment they are running synchronously.

> @fkleuver I just realised in our computed observers, we need to tweak the change handling timing as well. At the moment they are running synchronously. And the last step...

Nice work @fkleuver , there's one more place we will need to look into: currently with synchronous timing, we have change handler callback invoked after subscribers. Like the following example:...

You are right @ekzobrain , its originally intended to be staying in sync mode, while the computed observers moved to async. Somewhere along the way I got lost of this...