Skip to content
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

String based parser: Sort and distinct does allow using public field name #4550

Closed
sync-by-unito bot opened this issue Mar 23, 2021 · 2 comments · Fixed by #4555
Closed

String based parser: Sort and distinct does allow using public field name #4550

sync-by-unito bot opened this issue Mar 23, 2021 · 2 comments · Fixed by #4555
Assignees

Comments

@sync-by-unito
Copy link

sync-by-unito bot commented Mar 23, 2021

The string query parser is not able to find fields by their public field name on sort and distinct operations:

No property 'mHungarian' found on object type 'class_with_policy' specified in 'sort'

  • public name: "mHungarian"
  • inner name: hungarian
@clementetb
Copy link
Contributor

#4555 fixed the issue except for one corner case, name aliasing does not work when using the public field name on backlinks of RealmResults.

@LinkingObjects("columnRealmLink")
final private RealmResults<AllTypes> columnRealmBackLink = null;

distinct(columnRealmLink) = works
distinct(columnRealmBackLink)= does not work

@clementetb clementetb reopened this Mar 25, 2021
@clementetb
Copy link
Contributor

duplicate with #4524

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants