-
Notifications
You must be signed in to change notification settings - Fork 894
chore(site): remove users and pagination services #9932
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
cda4b4f
Move users loading to react-query
BrunoQuaresma 9b3adea
Remove pagination service
BrunoQuaresma 9db6ec6
Move suspend to react-query
BrunoQuaresma 7fb3858
Move activate to react-query
BrunoQuaresma 1a6fcfb
Remove missed suspend events
BrunoQuaresma 04fb5d3
Move delete to react-query
BrunoQuaresma 44d8de6
Move reset password to react-query
BrunoQuaresma 269f67f
Move update roles to react-query
BrunoQuaresma b4b7a77
Update copy and remove language object
BrunoQuaresma 76e94fb
Move auth methods queries to the users query module
BrunoQuaresma 50c861d
Add mock to deployment config and fix fragment warning
BrunoQuaresma 93e4e80
Fix tests
BrunoQuaresma 579cb11
Update UsersPage.tsx
BrunoQuaresma 5eb2321
Update UsersPageView.tsx
BrunoQuaresma 735fde8
Merge branch 'main' of https://github.com/coder/coder into bq/refacto…
BrunoQuaresma 57bb614
Merge branch 'bq/refactor-users-service' of https://github.com/coder/…
BrunoQuaresma 23517e3
Remove comments
BrunoQuaresma d2830ff
Merge branch 'main' of https://github.com/coder/coder into bq/refacto…
BrunoQuaresma File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next
Next commit
Move users loading to react-query
- Loading branch information
commit cda4b4f96149d769d49276ec96c9e8a368047c3c
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
should we really be using
req
as a key here? notreq.id
or something?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.
Req is basically the
page
,offset
andfilter
params so in this case I think makes sense to use them together. Reference: https://tanstack.com/query/v4/docs/react/guides/query-keys#query-keys-are-hashed-deterministicallyThere 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.
Yeah, it's not always needed, but I've seen the pattern where the payload for the query is treated as the last argument of the query key. It also makes it possible for the query function to access it via the
queryKey
property on its options argument, even if you extract the query function outside the hook