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

import issue fix #2000

Open
wants to merge 2 commits into
base: console
Choose a base branch
from
Open

import issue fix #2000

wants to merge 2 commits into from

Conversation

nabeelmd-eGov
Copy link
Contributor

@nabeelmd-eGov nabeelmd-eGov commented Dec 10, 2024

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

  • New Features
    • Enhanced the BoundaryWithDate component for improved date management and rendering.
  • Bug Fixes
    • Streamlined URL retrieval in the useProjectSearchWithBoundary function for better performance.
  • Chores
    • Removed unused imports in the BoundaryWithDate component to clean up the codebase.

@nabeelmd-eGov nabeelmd-eGov requested a review from a team as a code owner December 10, 2024 05:31
Copy link
Contributor

coderabbitai bot commented Dec 10, 2024

📝 Walkthrough

Walkthrough

The pull request introduces modifications to the BoundaryWithDate component and the useProjectSearchWithBoundary hook. In BoundaryWithDate.js, unused imports are removed, and a local icon import is added. The component's internal state management and rendering logic remain primarily unchanged. In useProjectSearchWithBoundary.js, the url variable's scope is altered to be declared within a mapping function, ensuring it is fetched anew for each boundary. Overall, the changes streamline the component and enhance the function's structure without altering their core functionalities.

Changes

File Change Summary
health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/BoundaryWithDate.js Removed unused imports and added a local icon import; maintained state management and rendering logic.
health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/hooks/useProjectSearchWithBoundary.js Changed url variable declaration to be local within the map function for each boundary.

Possibly related PRs

Suggested reviewers

  • nipunarora-eGov

🐇 In the code, I hop and play,
Cleaning imports, brightening the way.
Dates are managed, all in line,
With boundaries set, everything's fine!
A sprinkle of icons, a tidy spree,
In this code garden, joyfully we see! 🌼


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. (Experiment)
  • @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: 0

🧹 Outside diff range comments (3)
health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/BoundaryWithDate.js (3)

Line range hint 9-11: Remove redundant commented code.

The line // const { t } = useTranslation(); is redundant as it's already declared above.

  const { t } = useTranslation();
  const tenantId = Digit.ULBService.getCurrentTenantId();
- // const { t } = useTranslation();

Line range hint 31-71: Consider refactoring date validation logic for better maintainability.

The date handling logic is repeated across handleDateChange and handleCycleDateChange. Consider extracting the common validation logic into a utility function.

+const isValidDate = (date, today) => {
+  return typeof date !== "undefined" && date > today;
+};

 const handleDateChange = ({ date, endDate = false, cycleDate = false, cycleIndex }) => {
-  if (typeof date === "undefined" || date <= today) {
+  if (!isValidDate(date, today)) {
     return null;
   }
   // ... rest of the function
 };

 const handleCycleDateChange = ({ date, endDate = false, cycleIndex }) => {
-  if (typeof date === "undefined" || date <= today) {
+  if (!isValidDate(date, today)) {
     return null;
   }
   // ... rest of the function
 };

Line range hint 134-146: Improve readability of date validation logic.

The validation logic in the FieldV1 components uses complex nested ternary operations and inline date calculations. Consider extracting these into helper functions for better readability and maintainability.

+const getMinStartDate = (index, cycleDates, today, startDate) => {
+  if (index > 0 && cycleDates?.find((j) => j.cycleIndex == index)?.endDate) {
+    const prevCycleEndDate = new Date(cycleDates?.find((j) => j.cycleIndex == index)?.endDate);
+    return new Date(prevCycleEndDate.getTime() + ONE_DAY_IN_MS).toISOString().split("T")[0];
+  }
+  return today >= startDate ? today : startDate;
+};

 populators={{
   validation: {
-    min: index > 0 && !isNaN(new Date(cycleDates?.find((j) => j.cycleIndex == index)?.endDate)?.getTime())
-      ? new Date(new Date(cycleDates?.find((j) => j.cycleIndex == index)?.endDate)?.getTime() + ONE_DAY_IN_MS)
-          ?.toISOString()
-          ?.split("T")?.[0]
-      : today >= startDate
-      ? today
-      : startDate,
+    min: getMinStartDate(index, cycleDates, today, startDate),
     max: endDate,
   },
 }}
📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Reviewing files that changed from the base of the PR and between b3c48dc and 999cc51.

📒 Files selected for processing (2)
  • health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/BoundaryWithDate.js (1 hunks)
  • health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/hooks/useProjectSearchWithBoundary.js (0 hunks)
💤 Files with no reviewable changes (1)
  • health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/hooks/useProjectSearchWithBoundary.js
🧰 Additional context used
📓 Path-based instructions (1)
health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/BoundaryWithDate.js (1)

Pattern **/*.js: check

🔇 Additional comments (1)
health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/BoundaryWithDate.js (1)

4-5: LGTM! Import cleanup improves code maintainability.

The removal of unused imports and addition of only necessary components helps reduce bundle size and improves code clarity.

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.

3 participants