-
Notifications
You must be signed in to change notification settings - Fork 98
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
Evaluating "new DateTime(2022,1,20)" does not work unless OptionInlineNamespacesEvaluationActive is turned on #127
Comments
Hello @HelgeL thanks for the issue. It should work again in version 1.4.36.0 |
Version 1.4.36.0 is published |
Wow, Grüezi and thank you for your quick fix! That's awesome. (Can I donate somehow?) |
Found the donate button, never mind! |
WOW thanks a lot @HelgeL for your donation |
Can be useful. I see that it is an option so normally it should not break compatibility. Just some questions : We just should add some documentation on it. |
Still using this fantastic library and great to see it progresses! I have made a huge version jump from 1.4.12.0 to current 1.4.35.0. However one of my tests does not pass anymore, so I have fiddled around.
When evaluating this expression:
new DateTime(2022,1,20)
the result is correctly evaluated with
OptionInlineNamespacesEvaluationActive=true
.However when
OptionInlineNamespacesEvaluationActive=false
(which was my default setting), an error is raised as follows:Type or class DateTime is unknown
The old version could successfully evaluate this expression regardless of OptionInlineNamespacesEvaluationActive setting. Maybe it is on purpose in which case I'm fine with turning the option on. I was just hesitating with the possible performance and security implications.
The text was updated successfully, but these errors were encountered: