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

BUGFIX|HCMPRE-1438: Updated payments Config key #2182

Merged
merged 1 commit into from
Feb 3, 2025

Conversation

Ramkrishna-egov
Copy link
Contributor

@Ramkrishna-egov Ramkrishna-egov commented Jan 31, 2025

Choose the appropriate template for your PR:

Feature PR

Feature Request

JIRA ID

Module

Description

Related Issues


Bugfix PR

Bugfix Request

JIRA ID

Module

Description

Root Cause

Related Issues


Release PR

Summary by CodeRabbit

  • Bug Fixes

    • Updated session storage key from "paymentConfig" to "paymentsConfig" across multiple components to ensure correct configuration retrieval
    • Modified configuration data retrieval in payments module initialization
  • New Features

    • Introduced a new hierarchyType variable in payments initialization service to improve configuration handling

@Ramkrishna-egov Ramkrishna-egov requested a review from a team as a code owner January 31, 2025 10:59
Copy link
Contributor

coderabbitai bot commented Jan 31, 2025

📝 Walkthrough

Walkthrough

The pull request introduces a series of changes across multiple files in the health payments module, primarily focusing on modifying the session storage key used for retrieving payment configurations. The key is changed from "paymentConfig" to "paymentsConfig" in several components, including BoundaryComponent, filter_section, BillInbox, and project_selection. Additionally, a new variable hierarchyType is introduced in the PaymentsInitialization service to determine the hierarchy type for boundary data fetching.

Changes

File Change Summary
.../BoundaryComponent.js Updated session storage key from "paymentConfig" to "paymentsConfig"
.../attendance_inbox/filter_section.js Modified session storage retrieval to use "paymentsConfig"
.../bill_inbox/BillInbox.js Changed session storage key to "paymentsConfig"
.../pages/employee/project_selection.js Updated session storage key retrieval
.../services/PaymentsInitialization.js Added hierarchyType variable from window?.globalConfigs

Sequence Diagram

sequenceDiagram
    participant UI as User Interface
    participant SS as Session Storage
    participant IS as Initialization Service
    
    UI->>SS: Request payment configuration
    SS-->>UI: Return configuration with new key "paymentsConfig"
    UI->>IS: Fetch boundary data
    IS->>IS: Determine hierarchyType
    IS-->>UI: Return boundary information
Loading

Possibly related PRs

Suggested reviewers

  • nipunarora-eGov
  • jagankumar-egov

Poem

🐰 A Rabbit's Ode to Configuration Keys 🔑

From "paymentConfig" to "paymentsConfig" we leap,
A tiny change that makes our data weep,
Boundaries dance with a new storage might,
Configurations now aligned just right!
Hop, hop, hooray for cleaner code today! 🎉

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6c84b84 and 210e1e6.

📒 Files selected for processing (5)
  • health/micro-ui/web/micro-ui-internals/packages/modules/health-payments/src/components/BoundaryComponent.js (1 hunks)
  • health/micro-ui/web/micro-ui-internals/packages/modules/health-payments/src/components/attendance_inbox/filter_section.js (2 hunks)
  • health/micro-ui/web/micro-ui-internals/packages/modules/health-payments/src/components/bill_inbox/BillInbox.js (1 hunks)
  • health/micro-ui/web/micro-ui-internals/packages/modules/health-payments/src/pages/employee/project_selection.js (1 hunks)
  • health/micro-ui/web/micro-ui-internals/packages/modules/health-payments/src/services/PaymentsInitialization.js (2 hunks)
🧰 Additional context used
📓 Path-based instructions (5)
health/micro-ui/web/micro-ui-internals/packages/modules/health-payments/src/components/BoundaryComponent.js (1)

Pattern **/*.js: check

health/micro-ui/web/micro-ui-internals/packages/modules/health-payments/src/pages/employee/project_selection.js (1)

Pattern **/*.js: check

health/micro-ui/web/micro-ui-internals/packages/modules/health-payments/src/components/attendance_inbox/filter_section.js (1)

Pattern **/*.js: check

health/micro-ui/web/micro-ui-internals/packages/modules/health-payments/src/services/PaymentsInitialization.js (1)

Pattern **/*.js: check

health/micro-ui/web/micro-ui-internals/packages/modules/health-payments/src/components/bill_inbox/BillInbox.js (1)

Pattern **/*.js: check

⏰ Context from checks skipped due to timeout of 10000ms (2)
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: Analyze (actions)
🔇 Additional comments (5)
health/micro-ui/web/micro-ui-internals/packages/modules/health-payments/src/services/PaymentsInitialization.js (1)

118-118: LGTM!

The hierarchyType parameter is correctly used in the boundary relationships search request.

health/micro-ui/web/micro-ui-internals/packages/modules/health-payments/src/components/attendance_inbox/filter_section.js (1)

11-11: Verify the session storage key update across the codebase.

The session storage key has been updated from "paymentConfig" to "paymentsConfig". This change appears to be part of a coordinated update across multiple files.

Let's verify that this change is consistent across the codebase and that there are no remaining instances of the old key:

Also applies to: 118-118

health/micro-ui/web/micro-ui-internals/packages/modules/health-payments/src/pages/employee/project_selection.js (1)

30-30: Session storage key update is consistent.

The update from "paymentConfig" to "paymentsConfig" matches the changes in other files.

health/micro-ui/web/micro-ui-internals/packages/modules/health-payments/src/components/BoundaryComponent.js (1)

19-19: Session storage key update is consistent.

The update from "paymentConfig" to "paymentsConfig" matches the changes in other files.

health/micro-ui/web/micro-ui-internals/packages/modules/health-payments/src/components/bill_inbox/BillInbox.js (1)

40-40: Session storage key update is consistent.

The update from "paymentConfig" to "paymentsConfig" matches the changes in other files.

Let's verify the data migration for existing session storage:

✅ Verification successful

Session storage implementation is correct and consistent

The codebase exclusively uses the "paymentsConfig" key, with proper initialization in Module.js. No instances of the old key "paymentConfig" were found, indicating this is either a new feature or a clean implementation. No data migration is necessary.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any session storage initialization or migration logic
echo "Searching for session storage initialization..."
rg -A 5 "Digit\.SessionStorage\.set\(\"paymentsConfig\"" --type js

# Search for any initialization service or configuration setup
echo -e "\nSearching for configuration setup..."
ast-grep --pattern 'const $_ = {
  $$$
  paymentsConfig: $_,
  $$$
}'

Length of output: 1026


Script:

#!/bin/bash
# Search for old key usage
echo "Searching for old key usage..."
rg "Digit\.SessionStorage\.(get|set)\(\"paymentConfig\"" --type js

# Search for any migration logic
echo -e "\nSearching for migration logic..."
rg -B 3 -A 3 "paymentConfig.*paymentsConfig" --type js

Length of output: 1550

@Ramkrishna-egov Ramkrishna-egov changed the title Updated paymentsConfig Key BUGFIX|HCMPRE-1438: Updated payments Config key Jan 31, 2025
@jagankumar-egov jagankumar-egov merged commit 1482930 into console Feb 3, 2025
6 of 9 checks passed
@jagankumar-egov jagankumar-egov deleted the payment-config branch February 3, 2025 05:19
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.

2 participants