-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
Implement filter offset for attribute values API #6667
base: master
Are you sure you want to change the base?
Conversation
7844d60
to
4026433
Compare
5f3026a
to
b25a4b3
Compare
9a63a0e
to
66cf01c
Compare
❌ 1 Tests Failed:
View the top 1 failed tests by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My main concern is that your test could be using offset
by default rather than filter_offset
447e323
to
e1e5eae
Compare
e1e5eae
to
7e58b8b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM assuming the tests pass
7e58b8b
to
0fb48b0
Compare
https://github.com/getsentry/eap-planning/issues/115
Already did it for attribute names API, doing it for attribute values API in this PR. Also sorted attribute values alphabetically in response so filter offset can be implemented