We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The current version of mogenerator (1.24) does not handle variable expressions in fetch requests correctly.
Description & steps in order to reproduce the issue:
World ---- countries ---->> Country ---- cities ---->> City
The entity "City" has an attribute named "testAttribute". In addition the model also contains a fetch request with a variable expression:
Fetch all "World" objects where: Expression: countries.cities.testAttribute == $testExpression
Observations:
I have tried down to track down the issue myself - here is what I found out: The method
- (void)_processPredicate:(NSPredicate*)predicate_ bindings:(NSMutableArray*)bindings_
contains the code that handles a single predicate. This method calls _resolveKeyPathType where the crash occurs.
The text was updated successfully, but these errors were encountered:
I had this same problem.
@ChristianKienle thank you for figuring out the issue.
Sorry, something went wrong.
Dup of #15
No branches or pull requests
The current version of mogenerator (1.24) does not handle variable expressions in fetch requests correctly.
Description & steps in order to reproduce the issue:
World ---- countries ---->> Country ---- cities ---->> City
The entity "City" has an attribute named "testAttribute". In addition the model also contains a fetch request with a variable expression:
Fetch all "World" objects where:
Expression: countries.cities.testAttribute == $testExpression
Observations:
I have tried down to track down the issue myself - here is what I found out: The method
contains the code that handles a single predicate. This method calls _resolveKeyPathType where the crash occurs.
The text was updated successfully, but these errors were encountered: