Still yet ParseException after update from v.1.0.8.18 to 1.0.9.0 or any newer (till 1.3.7)

[OlegNadymov]

Still yet ParseException after update from v.1.0.8.18 to 1.0.9.0 or any newer (till 1.3.7)

[OlegNadymov]

It seems to be working now 👍

[StefH]

@OlegNadymov
Can you provide the full "User" class?

[StefH]

#760

[StefH]

@OlegNadymov
I could not test it 100% (due to missing User class), but I've updated the code.

Can you try 1.3.8-preview-02?

[StefH]

you probably need 1.3.8-preview-03

[OlegNadymov]

Unfortunately, again ParseException: ')' or ',' expected.

I see that now inner statements have the same number of quoutes (two):

{Param_0 => In(Param_0.Id, SubSelect("Identity", "LegalPerson", Concat(Concat("StaticHelper.In(ParentId, StaticHelper.SubSelect(""LegalPersonId"", ""PointSiteTD"", ""Identity = ", ToExpressionString(Get("CurrentPlace"), 2)), """, """"))"), ""))}

But in the old version they had one single quote:

{Param_0 => In(Param_0.Id, SubSelect("Identity", "LegalPerson", Concat(Concat("StaticHelper.In(ParentId, StaticHelper.SubSelect("LegalPersonId", "PointSiteTD", "Identity = ", ToExpressionString(Get("CurrentPlace"), 2)), "", ""))"), ""))}

So, when I try to DynamicInvoke the complied expression I have the exception here:

BTW, I use the same User class from your tests, but I've added new three properties as you did here:
#760

[StefH]

Can you try preview-4?

[StefH]

Thanks for verifying. Please do some more tests, and if it's working good, close this issue.

[OlegNadymov]

Ok! I'm trying to check if it works for a deeper level. I think, I don't have expressions with deeper levels. But I'm wondering if it works.

[OlegNadymov]

All my tests are passed successfully. So, I will be looking forward for release these features to upgrade your package on my production.

[StefH]

@OlegNadymov
I'll merge this PR to master.

I've no date yet on a new release. I'll keep you informed.

[OlegNadymov]

@StefH thanks for the information! 👍