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.

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

Citizen logout redirect #1627

Open
wants to merge 6 commits into
base: develop
Choose a base branch
from
Open

Conversation

mithunhegde-egov
Copy link

@mithunhegde-egov mithunhegde-egov commented Oct 23, 2024

due to usertype employee citizen logout was redirecting to employee login page.

Summary by CodeRabbit

  • New Features

    • Users are now redirected to the login page immediately after logging out, enhancing the logout experience.
  • Bug Fixes

    • The sidebar now displays a loading state when link data is being fetched, improving user feedback during data loading.

@mithunhegde-egov mithunhegde-egov requested a review from a team as a code owner October 23, 2024 02:22
Copy link
Contributor

coderabbitai bot commented Oct 23, 2024

📝 Walkthrough

Walkthrough

The changes in this pull request modify the handleOnSubmit function of the StaticCitizenSideBar component to include a redirect to the login page after a user logs out. Additionally, the Loader component is now conditionally rendered based on the islinkDataLoading state, providing a visual indication when link data is being fetched. The overall structure and logic of the sidebar remain unchanged, with no significant alterations to functionality or error handling.

Changes

File Change Summary
micro-ui/web/micro-ui-internals/packages/modules/core/src/components/TopBarSideBar/SideBar/StaticCitizenSideBar.js Modified handleOnSubmit to redirect to the login page after logout and added conditional rendering of the Loader component.

Possibly related PRs

Suggested reviewers

  • jagankumar-egov

🐰 In the sidebar, where users roam,
A logout now leads them home.
With a loader to show,
As data does flow,
To the login page, they’ll soon comb! 🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Files that changed from the base of the PR and between 3107594 and 46c0916.

📒 Files selected for processing (1)
  • micro-ui/web/micro-ui-internals/packages/modules/core/src/components/TopBarSideBar/SideBar/StaticCitizenSideBar.js (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
micro-ui/web/micro-ui-internals/packages/modules/core/src/components/TopBarSideBar/SideBar/StaticCitizenSideBar.js (1)

Pattern **/*.js: check

🔇 Additional comments (2)
micro-ui/web/micro-ui-internals/packages/modules/core/src/components/TopBarSideBar/SideBar/StaticCitizenSideBar.js (2)

Line range hint 108-110: LGTM! Clean implementation of loading state.

The conditional rendering of the Loader component is implemented correctly using the early return pattern.


99-99: Verify no hardcoded employee login redirects exist.

Let's ensure there are no other components that might override this redirect behavior.

✅ Verification successful

Let me try a different search strategy to verify this concern.

This should help us find:

  1. All login-related redirects
  2. Logout handling logic
  3. Specific citizen login/logout flows

Based on the search results, I can now provide a definitive response:

No hardcoded employee login redirects found in citizen logout flows

The codebase search reveals that:

  1. All citizen-related logout redirects consistently point to /citizen/login
  2. The only employee login redirect exists in a generic utility (Request.js) that properly handles both citizen and employee cases using a conditional check
  3. The logout implementation in StaticCitizenSideBar.js follows the correct pattern for citizen redirects

The changes in the PR are consistent with the existing logout behavior across the codebase.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for potential hardcoded employee login redirects in citizen flows
rg -l "employee/login" | xargs rg "citizen.*logout" -C 3

# Search for other logout handlers that might need similar updates
ast-grep --pattern 'UserService.logout()' 

Length of output: 100


Script:

#!/bin/bash
# Search for login/logout related redirects in the codebase
rg -g '*.js' -g '*.jsx' "window\.location\.href.*login" -C 2

# Search for logout handlers
rg -g '*.js' -g '*.jsx' "logout" -C 2

# Search specifically for citizen related paths
rg -g '*.js' -g '*.jsx' "citizen.*login|login.*citizen" -C 2

Length of output: 24686

@@ -96,7 +96,7 @@ const StaticCitizenSideBar = ({ linkData, islinkDataLoading }) => {
const handleOnSubmit = () => {
Digit.UserService.logout();
setShowDialog(false);
};
window.location.href = `/${window?.contextPath}/citizen/login`; };
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Add error handling for logout operation.

While the redirect logic is correct, consider handling potential logout failures before redirecting.

Consider this implementation:

- window.location.href = `/${window?.contextPath}/citizen/login`;
+ try {
+   await Digit.UserService.logout();
+   setShowDialog(false);
+   window.location.href = `/${window?.contextPath}/citizen/login`;
+ } catch (error) {
+   console.error('Logout failed:', error);
+   // Show error notification to user
+   Digit.Hooks.useToast.error(t('LOGOUT_ERROR'));
+ }

Committable suggestion was skipped due to low confidence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant