Patch for file name

[ashish-egov]

Summary by CodeRabbit

• New Features

  • Enhanced file upload functionality with tracking of the uploaded file's name.

• Bug Fixes

  • Improved error handling and user feedback during file upload and validation processes.

[coderabbitai]

📝 Walkthrough

Walkthrough

The UserUpload component has been updated to improve file upload handling and state management. Key modifications include the addition of a fileName property in the request body during the onSubmit function, allowing the filename to be sent to the server. Error handling in the fetchData function has been enhanced for better feedback to users, and the onBulkUploadSubmit function has been adjusted to ensure the filename is correctly stored in the component's state.

Changes

File	Change Summary
health/micro-ui/web/micro-ui-internals/packages/modules/microplan/src/components/UserUpload.js	- Added fileName property to the request body in onSubmit function. - Enhanced error handling in fetchData function. - Updated onBulkUploadSubmit to correctly set the uploaded file's name in the state.

Possibly related PRs

• Update UploadDataCustom.js #1493: The UploadDataCustom component has been modified to enhance file upload functionality, which is directly related to the changes made in the UserUpload component regarding file handling and state management.
• Added some enhancement in upload screen #1515: This PR includes updates to the UploadDataCustom component that improve file upload processes, aligning with the enhancements made in the UserUpload component for managing file uploads and user feedback.
• Added request Info in generate request #1519: Changes in the UploadDataCustom component focus on file upload and validation processes, which are relevant to the modifications in the UserUpload component that also enhance file upload handling.
• Update UploadDataCustom.js #1524: The updates to the UploadDataCustom component regarding error handling and file upload management are closely related to the changes made in the UserUpload component.
• Update UploadDataCustom.js #1528: Enhancements in the UploadDataCustom component for file handling and user feedback mechanisms are directly relevant to the changes made in the UserUpload component.

🐰 In the meadow, the files take flight,
With fileName now shining bright.
Errors handled with care and grace,
Uploads now find their rightful place.
Hopping along, we cheer and play,
For smoother uploads, hip-hip-hooray! 🎉

---

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

• 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.
  • 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.

[coderabbitai]

Actionable comments posted: 1

🧹 Outside diff range comments (1)

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

Line range hint 90-106: Improved error handling and parsing

The changes in the fetchData function enhance error handling and provide more detailed error messages. This is a good improvement for user experience and debugging.

Consider using a separate function for error parsing to improve readability and maintainability. For example:

const parseErrorMessage = (error) => {
  try {
    const parsedError = JSON.parse(error);
    return parsedError?.description || parsedError?.message || t("HCM_VALIDATION_FAILED");
  } catch (e) {
    console.error("Error parsing JSON:", e);
    return t("HCM_VALIDATION_FAILED");
  }
};

Then you can use it in your code like this:

const errorMessage = temp?.additionalDetails?.error 
  ? parseErrorMessage(temp.additionalDetails.error)
  : t("HCM_VALIDATION_FAILED");
setShowToast({ key: "error", label: errorMessage, transitionTime: 5000000 });

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Files that changed from the base of the PR and between 0508e7b and 4cfcbf0.

📒 Files selected for processing (1)

• health/micro-ui/web/micro-ui-internals/packages/modules/microplan/src/components/UserUpload.js (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

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

Pattern **/*.js: check

🔇 Additional comments (1)

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

Line range hint 186-189: Improved file name handling and error messages

The changes in the onBulkUploadSubmit function enhance file name handling and provide more specific error messages. This is a good improvement for user experience.

The addition of setFileName(file?.[0]?.name) ensures that the file name is correctly stored in the component's state, which can be useful for further operations or display purposes.

The use of more specific error messages (e.g., t("HCM_ERROR_FILE_UPLOAD_FAILED") instead of a generic error message) helps users understand what went wrong more clearly.

Also applies to: 200-201