-
-
Notifications
You must be signed in to change notification settings - Fork 224
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
Doc: Method call in custom type raises "No applicable method '' exists in type ''" ParseException #721
Labels
Comments
jhpetersen
changed the title
params array in custom type method raises "No applicable method '' exists in type ''" ParseException
method call in custom type method raises "No applicable method '' exists in type ''" ParseException
Jul 7, 2023
jhpetersen
changed the title
method call in custom type method raises "No applicable method '' exists in type ''" ParseException
method call in custom type raises "No applicable method '' exists in type ''" ParseException
Jul 7, 2023
@jhpetersen this issue is related to #727 Workaround is using different name for input from type |
Wow, thanks, i would never have suspected that to be the cause 😮 👍
(Nevertheless should be fixed or well documented..) |
StefH
changed the title
method call in custom type raises "No applicable method '' exists in type ''" ParseException
Doc: Method call in custom type raises "No applicable method '' exists in type ''" ParseException
Sep 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1. Description
I am trying to upgrade from Linq.Dynamic.Core 1.2.25 to 1.3.3 and facing runtime ParserExcpetions on DynamicExpressionParser.ParseLambda call
No applicable method 'SomeMethod' exists in type 'MyCustomType'
.I've read the note on breaking change from 1.3.0 about having to register any classes from which a method should be callable (tested both ways with an attribute and a custom type provider), but that is not the problem (otherwise a
Methods on type 'MyCustomType' are not accessible
would have been thrown).2. Exception
Exception from the first fiddle:
3. Fiddle or Project
I created two test fiddles:
one demonstrating the issue with 1.3.3 and a second working with 1.2.25
4. Any further technical details
If one adds the DynamicLinqType() Attribute on MyCustomClass in the second fiddle, a similar exception is thrown, so this probably has something to do with handling member access in custom types in general.
(i would have digged deeper to find the root cause, but could not download symbol files from nuget server, so debugging inside DynamicLinq.Core was not possible)
Thanks for any help on this
The text was updated successfully, but these errors were encountered: