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

Added request Info in generate request #1519

Merged
merged 1 commit into from
Oct 15, 2024
Merged

Conversation

ashish-egov
Copy link
Contributor

@ashish-egov ashish-egov commented Oct 15, 2024

Summary by CodeRabbit

  • New Features

    • Enhanced file upload process with improved validation and error handling.
    • Added toast notifications for user feedback during uploads and validation.
    • Introduced new functions for managing file uploads, deletions, and downloads.
    • Included timestamp and authentication details in data requests.
  • Bug Fixes

    • Improved handling of multiple file uploads and checks for successful uploads.

Copy link
Contributor

coderabbitai bot commented Oct 15, 2024

📝 Walkthrough

Walkthrough

The UploadDataCustom component has been significantly updated to improve the file upload and validation processes. Key changes include the addition of a timestamp in the request body, a new forceUpdate parameter, and enhanced error handling mechanisms. The component now conditionally executes data fetching based on the presence of boundaryHierarchy and includes refined logic for handling multiple file uploads. Additionally, user feedback features have been improved, including toast notifications for various states, and several new functions have been introduced to manage file details and downloads.

Changes

File Change Summary
health/micro-ui/web/micro-ui-internals/packages/modules/microplan/src/components/UploadDataCustom.js - Modified UploadDataCustom component to enhance file upload and validation processes.
- Added timestamp, forceUpdate, authToken, and msgId to request body.
- Introduced new functions: updateUrlParams, enrichFileDetails, onBulkUploadSubmit, onFileDelete, onFileDownload, and downloadTemplate.
- Improved error handling and user feedback mechanisms, including toast notifications.

Possibly related PRs

  • Update UploadDataCustom.js #1493: This PR directly modifies the UploadDataCustom component, enhancing its file upload and validation functionality, which aligns closely with the changes made in the main PR.
  • Added some enhancement in upload screen #1515: This PR also includes changes to the UploadDataCustom component, specifically related to the fetchData function and error handling during file uploads, making it relevant to the main PR's focus on improving file upload processes.

Suggested reviewers

  • nipunarora-eGov

🐰 In the meadow, files do play,
With uploads dancing, come what may.
A timestamp added, errors tamed,
Toasts of feedback, all acclaimed.
In the burrow, joy's the theme,
For every file, a happy dream! 🌼


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

🧹 Outside diff range comments (2)
health/micro-ui/web/micro-ui-internals/packages/modules/microplan/src/components/UploadDataCustom.js (2)

Line range hint 253-264: Incorrect use of async function in useEffect

Using an async function directly as the argument to useEffect is not recommended because useEffect expects the function to either return undefined or a cleanup function, but async functions return a Promise. Instead, define the async function inside the useEffect and invoke it.

Apply this diff to correct the code:

-useEffect(async () => {
+useEffect(() => {
+  const fetchReadMeInfo = async () => {
     if (readMe?.["HCM-ADMIN-CONSOLE"]) {
       const newReadMeFacility = await translateReadMeInfo(
         readMe?.["HCM-ADMIN-CONSOLE"]?.ReadMeConfig?.filter((item) => item.type === `${type}-MP`)?.[0]?.texts
       );
       const newReadMeUser = await translateReadMeInfo(
         readMe?.["HCM-ADMIN-CONSOLE"]?.ReadMeConfig?.filter((item) => item.type === `${type}-MP`)?[0]?.texts
       );
       const newReadMeboundary = await translateReadMeInfo(
         readMe?.["HCM-ADMIN-CONSOLE"]?.ReadMeConfig?.filter((item) => item.type === `${type}-MP`)?[0]?.texts
       );

       const readMeText = {
         boundary: newReadMeboundary,
         facilityWithBoundary: newReadMeFacility,
         userWithBoundary: newReadMeUser,
       };

       setReadMeInfo(readMeText);
     }
+  };
+  fetchReadMeInfo();
 }, [readMe?.["HCM-ADMIN-CONSOLE"], type]);

Line range hint 330-339: Incorrect usage of fileUrl inside mapping function

Inside the fileUrl.map() function, you are always accessing fileUrl?.[0]?.id, which will result in the same id for all items, potentially causing incorrect file associations. Instead, use i?.id to access the current item's id.

Apply this diff to fix the issue:

 const fileData = fileUrl
   .map((i) => {
     const urlParts = i?.url?.split("/");
     const fileName = file?.[0]?.name;
-    const id = fileUrl?.[0]?.id;
+    const id = i?.id;
     const fileType =
       type === "facilityWithBoundary"
         ? "facility"
         : type === "userWithBoundary"
           ? "user"
           : type === "boundary"
             ? "boundaryWithTarget"
             : type;

     return {
       filestoreId: id,
       resourceId: resourceId,
       filename: fileName,
       type: fileType,
     };
   })
   .map(({ id, ...rest }) => rest);
📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Files that changed from the base of the PR and between 842be89 and 363858a.

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

Pattern **/*.js: check

🔇 Additional comments (1)
health/micro-ui/web/micro-ui-internals/packages/modules/microplan/src/components/UploadDataCustom.js (1)

Line range hint 429-439: Potential infinite loop with useEffect dependency

The useEffect hook updates the URL parameters whenever key changes:

useEffect(() => {
  updateUrlParams({ key: key });
  window.dispatchEvent(new Event("checking"));
}, [key]);

Ensure that updateUrlParams does not cause a change in the key value, as this could lead to an infinite rendering loop by continually triggering the useEffect.

Consider reviewing the updateUrlParams function to confirm it doesn't modify key, and refactor if necessary to prevent unintended behavior.

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