Xriuk

The final string should be the concatenation of the specified strings for users with a VAT number (eg: `"AT1234567"`), or a `null` value for users without a VAT number. Now...

> I see that both arguments for the concatenation are inside of the `VatNumber` model now. Yes, and they themselves are not nullable inside VatNumber, but VatNumber itself can be...

`HandleNullPropagationOption.True` seems to solve the issue. Is there any reason why this is configurable and may be disabled by default (since it looks like the default option depends on the...

This solution is conflicting with `$expand`/`$select` query options as it generates a lot of ternary operators with null checks (eg: `$it == null ? null : $it.Prop == null ?...

@xuzhg The samples you provided are correct. This is another query, that with the current implementation works, and it shouldn't. Because here `$it` mistakenly refers to the `email` type while...

@xuzhg I was mistaken, `$it` seems to work in `$filter`. But, I have tested this, and it does not work in nested `$compute` expressions. `{{issue1432DollarIt_HostAddress}}/odata/Customers(1)?$expand=Orders($compute=$it/Name as Test;$select=Test)` Gets: ``` System.ArgumentException:...

@WanjohiSammy yes, that is correct, as I wrote above, this only happens for **contained entities** (navigation properties with `ContainsTarget="true"`), and only with `odata.metadata=full`. So this has something to do with...

Any updates on this?