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

The getFilter method will not allow a dot in the field name #7

Closed
Sjustein opened this issue Sep 7, 2024 · 0 comments · Fixed by #8
Closed

The getFilter method will not allow a dot in the field name #7

Sjustein opened this issue Sep 7, 2024 · 0 comments · Fixed by #8
Assignees

Comments

@Sjustein
Copy link
Collaborator

Sjustein commented Sep 7, 2024

When passing a filter string with a property containing a dot, the part of the property before the dot will be ignored and only the part after the dot will be parsed and passed into the FilterClause built by the function.

Steps to reproduce:

  • Call the parser with a filter containing a dot in the property name.

Example:
?$filter=state.deleted eq false

The function handles dots in the value just fine.

@Sjustein Sjustein self-assigned this Sep 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant