-
Notifications
You must be signed in to change notification settings - Fork 297
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
Add filtering by team, is_currently_oncall and search on the user page #4575
Conversation
}); | ||
}; | ||
|
||
applyFilters = () => { |
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.
Seems this method is unused, can we remove it? Not related to your changes but there's another unused method in this component - renderContacts
, we could remove it too
if filter_name is not None: | ||
filter_options = list(filter(lambda f: filter_name in f["name"], filter_options)) |
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.
does the frontend use this search functionality? if not, I think it might make sense to remove this
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.
yes, it does
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.
I can't find any usages in the frontend code 🤔 Am I missing something?
@@ -841,6 +842,25 @@ def export_token(self, request, pk) -> Response: | |||
return Response(status=status.HTTP_204_NO_CONTENT) | |||
return Response(status=status.HTTP_405_METHOD_NOT_ALLOWED) | |||
|
|||
@action(methods=["get"], detail=False) |
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.
I believe we have openapi docs for the /users
routes (code). do we need to add anything here to document this new endpoint?
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.
good point, added
6fd599c
to
0b8e69c
Compare
#4575) # What this PR does This PR adds filtering by team and is_currently_oncall on the user page ## Which issue(s) this PR closes Closes #4353 <!-- *Note*: if you have more than one GitHub issue that this PR closes, be sure to preface each issue link with a [closing keyword](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests#linking-a-pull-request-to-an-issue). This ensures that the issue(s) are auto-closed once the PR has been merged. --> ## Checklist - [ ] Unit, integration, and e2e (if applicable) tests updated - [ ] Documentation added (or `pr:no public docs` PR label added if not required) - [ ] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes.
What this PR does
This PR adds filtering by team and is_currently_oncall on the user page
Which issue(s) this PR closes
Closes #4353
Checklist
pr:no public docs
PR label added if not required)release:
). These labels dictate how your PR willshow up in the autogenerated release notes.