Behaviour of !! operator has changed in 11.1 about avalonia HOT 6 CLOSED

It was documented

TIL, thanks. Either way, I agree that it's a regression.

This is not equivalent to any of the ObjectConverters.

True, I was referring specifically to the "null to boolean" conversion.

from avalonia.

We've decided that this issue is a serious enough regression that it necessitates an rc2.

from avalonia.

"!!" wasn't a defined and documented feature before. I would recommend using more explicit ObjectConverters.IsNotNull.

from avalonia.

"!!" wasn't a defined and documented feature before. I would recommend using more explicit ObjectConverters.IsNotNull.

It was documented. From the link I posted above:

"You can also use the negation operator twice. For example, where you want to perform the conversion from integer to Boolean, and then negate that value."

This is not equivalent to any of the ObjectConverters.

from avalonia.

Definitely looks like a regression introduced by the binding system refactor, will investigate.

Not sure if this is a showstopper and needs to be fixed for 11.0.0 or whether it can wait for 11.0.1 though.

from avalonia.

I've confirmed that this issue is fixed for me in 11.1.0-RC2.

from avalonia.