Optimize user data fetching and api logic #11
Merged
Conversation
This file contains 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
- Installed **Vitest** for `unit testing` framework. - Created test cases for the `formatDate` utility function to ensure correct formatting of valid date strings. - Added validation tests for `username`, `email`, `password`, and `confirm password` fields to verify proper validation logic. - Updated the testing configuration to support the new tests and ensure they run successfully.
- Implemented tests for the `useResize` hook to verify behavior across different screen sizes. - Added tests for the `useTheme` hook to check the default theme and verify that it updates to light or dark when changed.
- Added a test to ensure the `ThemeProvider` correctly applies the selected `theme` to the document's `root` element. - Mocked `localStorage` to return a predefined `theme` value for testing. - Verified that the appropriate `class` is applied to `document.documentElement` based on the `theme`.
- Implemented tests for `userStore` to verify user state and persistence in session storage. - Created tests for `authStore` to ensure authentication logic and state management function correctly.
Implemented tests for the following **AuthService** methods: - `signIn`: Verified successful sign-in and error handling. - `signUp`: Tested user registration process and error responses. - `signOut`: Checked the sign-out functionality. - `verifyEmail`: Confirmed email verification process. - `resendVerify`: Ensured resend verification logic works as expected. - `verifyToken`: Tested token verification and error handling. - `forgotPassword`: Validated forgot password request handling. - `resetPassword`: Checked password reset process. - `changePassword`: Tested password change functionality.
- Created unit tests for `AuthGuard` and `PrivateGuard` components to ensure proper functionality. - Verified that guards correctly redirect unauthorized users and allow access for authorized users.
- Added `Select` to the user retrieval query to minimize the data fetched from the database, improving performance and reducing memory usage. - Updated the user object with the latest information fetched from the verifyToken function, ensuring that only the necessary fields are loaded and modified. - This change enhances the efficiency of user operations by focusing on relevant fields during database interactions.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Selectto the user retrieval queryto minimize the data fetched from the database,
improving performance and reducing memory usage.
fetched from the verifyToken function, ensuring that
only the necessary fields are loaded and modified.
by focusing on relevant fields during database interactions.