-
-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Still yet ParseException after update from v.1.0.8.18 to 1.0.9.0 or any newer (till 1.3.7) #759
Comments
@OlegNadymov |
@OlegNadymov Can you try |
you probably need |
Unfortunately, again I see that now inner statements have the same number of quoutes (two):
But in the old version they had one single quote:
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: |
Can you try preview-4? |
It seems to be working now 👍 |
Thanks for verifying. Please do some more tests, and if it's working good, close this issue. |
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. |
All my tests are passed successfully. So, I will be looking forward for release these features to upgrade your package on my production. |
@OlegNadymov I've no date yet on a new release. I'll keep you informed. |
@StefH thanks for the information! 👍 |
1. Description
In continuation of #757
I have more complex string expressions with inner methods with inner string statements, e.g.:
The classes:
The above expression can be parsed on the preview version. But not invoked. I have ParseException during invoke.
I've found differencies how the old and the new version parse this expression:
The old version:
The new version:
Here starting with PointSiteTD statements there are two quotes in the new version instead single in the old version.
So, when I try to parse with expression inside
StaticHelper.SubSelect
to buildSqlExpression.Filter
I have the mentioned exception.2. Exception
Exception message:
3. Fiddle or Project
Again, I have done changes in DynamicExpressionParserTests only locally.
4. Any further technical details
It is working on v.1.0.8.18.
But it is not working on even version 1.3.8-preview-01.
The text was updated successfully, but these errors were encountered: