Change the value for meeting link and enable the grievance scheduler

[vanitha1822]

📋 Description

JIRA ID:

NA

---

✅ Type of Change

• 🐞 Bug fix (non-breaking change which resolves an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 🔥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 🛠 Refactor (change that is neither a fix nor a new feature)
• ⚙️ Config change (configuration file or build script updates)
• 📚 Documentation (updates to docs or readme)
• 🧪 Tests (adding new or updating existing tests)
• 🎨 UI/UX (changes that affect the user interface)
• 🚀 Performance (improves performance)
• 🧹 Chore (miscellaneous changes that don't modify src or test files)

---

ℹ️ Additional Information

Please describe how the changes were tested, and include any relevant screenshots, logs, or other information that provides additional context.

Summary by CodeRabbit

• Chores
  • Enabled the grievance data synchronization scheduler to run every 2 minutes.
  • Updated configuration for video call service to use direct property injection for meeting links.

[coderabbitai]

Walkthrough

The changes enable the grievance data synchronization scheduler in the CI environment and refactor the way a video call URL is injected into the VideoCallServiceImpl class, switching from manual property retrieval to Spring's @Value annotation for dependency injection.

Changes

File(s)	Change Summary
src/main/environment/common_ci.properties	Enabled the grievance data sync scheduler by setting start-grievancedatasync-scheduler to true.
src/main/java/com/iemr/common/service/videocall/VideoCallServiceImpl.java	Replaced manual property retrieval of the video call URL with Spring's @Value annotation field injection.

Sequence Diagram(s)

sequenceDiagram
    participant SpringContext
    participant VideoCallServiceImpl

    SpringContext->>VideoCallServiceImpl: Injects 'meetingLink' from 'video-call-url' property
    Note over VideoCallServiceImpl: 'meetingLink' field available for use

Loading

Poem

In the warren, schedulers awake,
Two-minute hops, for grievances’ sake.
With Spring’s embrace, a link appears,
No more manual fetching here!
Properties flow like carrot stew—
Oh, what a clever thing to do!
🥕

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 327321c and 23db093.

📒 Files selected for processing (2)

• src/main/environment/common_ci.properties (1 hunks)
• src/main/java/com/iemr/common/service/videocall/VideoCallServiceImpl.java (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: style-check / checkstyle
• GitHub Check: Build
• GitHub Check: Analyze (java)
• GitHub Check: Package-test

🔇 Additional comments (4)

src/main/environment/common_ci.properties (1)

173-173: LGTM! Scheduler enablement is clear and correct.

The change enables the grievance data synchronization scheduler as intended. The existing cron expression 0 0/2 * * * ? will run the scheduler every 2 minutes, which is appropriate for data synchronization.

src/main/java/com/iemr/common/service/videocall/VideoCallServiceImpl.java (3)

24-24: Good addition for dependency injection.

Adding the @Value import supports the refactoring to Spring's dependency injection pattern.

---

36-38: Excellent refactoring to use Spring's @value annotation.

This change moves from manual property retrieval to Spring's dependency injection, which is a best practice for configuration management.

---

43-44: Good cleanup of deprecated code.

Commenting out the old ConfigProperties-based approach is appropriate since it's been replaced with Spring's @value injection.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

[sonarqubecloud]

Quality Gate failed

Failed conditions
B Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE