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

changed template name #2032

Closed
wants to merge 2 commits into from
Closed

changed template name #2032

wants to merge 2 commits into from

Conversation

Bhavya-egov
Copy link
Contributor

@Bhavya-egov Bhavya-egov commented Dec 16, 2024

Summary by CodeRabbit

  • New Features

    • Enhanced file download functionality with dynamic filenames based on campaign context.
    • Introduced a popup to prompt users for template downloads only if not previously downloaded.
  • Bug Fixes

    • Improved error handling during file uploads and downloads with clearer feedback for users, including specific error messages for validation issues.

@Bhavya-egov Bhavya-egov requested a review from a team as a code owner December 16, 2024 06:05
Copy link
Contributor

coderabbitai bot commented Dec 16, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The pull request modifies the UploadData component in the campaign manager module, focusing on improving file download functionality and error handling. The changes introduce a new state variable downloadedTemplates to track template downloads, update the downloadTemplate function to use dynamic filenames based on the campaign name, and enhance the validateExcel function with more robust validation and error messaging.

Changes

File Change Summary
health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/UploadData.js - Added downloadedTemplates state variable
- Updated downloadTemplate function to use dynamic filename
- Improved error handling and validation logic

Possibly related PRs

Suggested reviewers

  • jagankumar-egov

Poem

🐰 Downloading templates with grace,
Filenames now dance with campaign's embrace.
Errors caught with a vigilant eye,
Templates tracked, no more a sigh.
Code hops forward, clean and bright! 🎉

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request.


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f3ae757 and 1fbf4f0.

📒 Files selected for processing (1)
  • health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/UploadData.js (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/UploadData.js (1)

Pattern **/*.js: check


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

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

Line range hint 432-486: Enhance boundary validation error messages.

The current validation logic for boundary data could be more specific about which validation failed. Consider aggregating similar errors and providing more context.

Apply this diff to improve error messages:

 const validateMultipleTargets = (workbook) => {
   let isValid = true;
   const targetError = [];
+  const errorsByType = {
+    missing: [],
+    range: [],
+    type: []
+  };

   for (let i = 0; i < workbook.SheetNames.length; i++) {
     // ... existing validation logic ...
     
     if (value === undefined || value === null) {
-      targetError.push(
+      errorsByType.missing.push(
         `${t("HCM_DATA_AT_ROW")} ${jsonData.indexOf(row) + 2} ${t("HCM_IN_COLUMN")} "${headersToValidate[j]}" ${t(
           "HCM_DATA_SHOULD_NOT_BE_EMPTY"
         )} at ${sheetName}`
       );
     } else if (value >= 100000000) {
-      targetError.push(
+      errorsByType.range.push(
         `${t("HCM_DATA_AT_ROW")} ${jsonData.indexOf(row) + 2} ${t("HCM_IN_COLUMN")} "${headersToValidate[j]}" ${t(
           "HCM_DATA_SHOULD_BE_LESS_THAN_MAXIMUM"
         )} at ${sheetName}`
       );
     }
     // ... rest of the validation ...
   }

+  // Aggregate errors by type
+  if (errorsByType.missing.length > 0) {
+    targetError.push(t("HCM_MISSING_VALUES_HEADER"));
+    targetError.push(...errorsByType.missing);
+  }
+  if (errorsByType.range.length > 0) {
+    targetError.push(t("HCM_INVALID_RANGES_HEADER"));
+    targetError.push(...errorsByType.range);
+  }
🧰 Tools
🪛 Biome (1.9.4)

[error] 1036-1036: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)


Line range hint 31-52: Optimize state management using reducer pattern.

The component manages multiple related states for errors, validation, and upload status. Consider using useReducer for better state management.

Example implementation:

const initialState = {
  uploadState: {
    isError: false,
    isSuccess: false,
    isValidation: false,
    apiError: null,
  },
  downloadState: {
    downloadError: false,
    downloadedTemplates: {
      boundary: false,
      facilityWithBoundary: false,
      user: false,
    }
  },
  errorsType: {},
};

const uploadReducer = (state, action) => {
  switch (action.type) {
    case 'SET_UPLOAD_ERROR':
      return {
        ...state,
        uploadState: { ...state.uploadState, isError: true, apiError: action.payload }
      };
    case 'SET_UPLOAD_SUCCESS':
      return {
        ...state,
        uploadState: { ...state.uploadState, isSuccess: true, isError: false }
      };
    // ... other cases
  }
};
🧰 Tools
🪛 Biome (1.9.4)

[error] 1036-1036: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)


Line range hint 1016-1042: Enhance download progress feedback.

The template download functionality could benefit from better visual feedback during the download process.

Apply this diff to add download progress indication:

 const downloadTemplate = async () => {
+  const [downloadProgress, setDownloadProgress] = useState(false);
+  
   await mutation.mutate(
     {
       params: {
         tenantId: tenantId,
         type: type,
         hierarchyType: params?.hierarchyType,
         campaignId: id,
       },
     },
     {
       onSuccess: async (result) => {
+        setDownloadProgress(true);
         if (result?.GeneratedResource?.[0]?.status === "failed") {
           setDownloadError(true);
           setShowToast({ key: "error", label: t("ERROR_WHILE_DOWNLOADING") });
+          setDownloadProgress(false);
           return;
         }
         // ... rest of the success handling
+        setDownloadProgress(false);
       },
       onError: (error, result) => {
         // ... error handling
+        setDownloadProgress(false);
       },
     }
   );
 };

+// Add loading indicator in the UI
+{downloadProgress && <LoaderWithGap text={"DOWNLOADING_TEMPLATE"} />}
🧰 Tools
🪛 Biome (1.9.4)

[error] 1036-1036: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5ba5a53 and f3ae757.

📒 Files selected for processing (1)
  • health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/UploadData.js (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/UploadData.js (1)

Pattern **/*.js: check

coderabbitai[bot]
coderabbitai bot previously approved these changes Dec 16, 2024
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