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.

Sign up for GitHub

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

Jump to bottom

RecordsRead should not fail if multiple values exist #739

Open
Tracked by #806
LiranCohen opened this issue May 14, 2024 · 0 comments
Open
Tracked by #806

RecordsRead should not fail if multiple values exist #739

LiranCohen opened this issue May 14, 2024 · 0 comments
Labels
feature New feature or request hacktoberfest For the hacking month of October

Comments

@LiranCohen
Copy link
Member

Currently, if there is more than one match to a RecordsRead filter, the operation will fail.

The desired behavior is to include an optional sort property for the read, which allows the user control over which record to return if there is more than one record matching the filter.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature New feature or request hacktoberfest For the hacking month of October
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@LiranCohen @thehenrytsai