adding map height css changes, geojson active inactive status change

[siddhant-nawale-egov]

No description provided.

[coderabbitai]

Walkthrough

Walkthrough

The updates primarily focus on minor version increments for CSS dependencies in HTML files and adjusting feature processing logic in a utility script. Specifically, CSS styles for the micro UI modules have been updated, and session management functionalities have been refined to ensure more robust feature handling.

Changes

File Path	Change Summary
.../example/public/index.html	Updated CSS link version from 1.0.45-microplan to 1.0.46-microplan.
health/micro-ui/web/public/index.html	CSS version incremented from 1.0.45 to 1.0.46.
.../packages/modules/hcm-microplanning/src/utils/updateSessionUtils.js	Enhanced feature processing logic; added constant UPLOADED_DATA_ACTIVE_STATUS

Poem

Amidst the lines of code so sleek,

A fresh new stylesheet we now seek.

From forty-five to forty-six we go,

Features evolve, in clear flow.

With sessions updated, precise and swift,

Our UI gets a neat little lift! 🌟

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ef3963f and f5f2f81.

Files selected for processing (3)

• health/micro-ui/web/micro-ui-internals/example/public/index.html (1 hunks)
• health/micro-ui/web/micro-ui-internals/packages/modules/hcm-microplanning/src/utils/updateSessionUtils.js (2 hunks)
• health/micro-ui/web/public/index.html (1 hunks)

Files skipped from review due to trivial changes (2)

• health/micro-ui/web/micro-ui-internals/example/public/index.html
• health/micro-ui/web/public/index.html

Additional context used

Path-based instructions (1)

health/micro-ui/web/micro-ui-internals/packages/modules/hcm-microplanning/src/utils/updateSessionUtils.js (1)

Pattern **/*.js: check

Learnings (1)

health/micro-ui/web/micro-ui-internals/packages/modules/hcm-microplanning/src/utils/updateSessionUtils.js (1)

User: siddhant-nawale-egov
PR: egovernments/DIGIT-Frontend#698
File: micro-ui/web/micro-ui-internals/packages/modules/hcm-microplanning/src/utils/updateSessionUtils.js:144-156
Timestamp: 2024-05-26T18:47:54.758Z
Learning: In the `updateSessionUtils.js` file, during the data processing phase, errors should be logged, and the file should be ignored without throwing exceptions.

Additional comments not posted (3)

health/micro-ui/web/micro-ui-internals/packages/modules/hcm-microplanning/src/utils/updateSessionUtils.js (3)

7-7: Enhance error handling by providing more specific error messages and logging.

Given the complexity of the data processing functions, it is crucial to have detailed error messages that can aid in troubleshooting.

-      reject(error);
+      reject(new Error(`Failed to handle Excel array buffer: ${error.message}`));
-      reject(error);
+      reject(new Error(`Failed to convert SHP to GeoJSON: ${error.message}`));
-      reject(error);
+      reject(new Error(`Failed to parse GeoJSON response: ${error.message}`));
-      reject(new Error("Error reading the blob data"));
+      reject(new Error(`Error reading the blob data: ${reader.error.message}`));

Likely invalid or redundant comment.

---

7-7: Consider using object destructuring for constants import.

Using object destructuring for importing multiple constants from a single module can improve readability and maintainability of the code.

- import { EXCEL, GEOJSON, SHAPEFILE, ACCEPT_HEADERS, LOCALITY, commonColumn, UPLOADED_DATA_ACTIVE_STATUS } from "../configs/constants";
+ import { EXCEL, GEOJSON, SHAPEFILE, ACCEPT_HEADERS, commonColumn, UPLOADED_DATA_ACTIVE_STATUS } from "../configs/constants";

Likely invalid or redundant comment.

---

7-7: Consider using a more sophisticated logging framework for better error tracking and resolution.

The current use of console.error for logging errors is basic and might not provide enough information for debugging in production environments.

- console.error(error?.message);
+ Digit.Logger.error(`Error while fetching boundary data: ${error.message}`, { error, additionalData: { tenantId: additionalProps.campaignData?.tenantId } });

Likely invalid or redundant comment.