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

BUGFIX/HCMPRE-965 : Incremented css version #2106

Merged
merged 2 commits into from
Jan 6, 2025

Conversation

Bhavya-egov
Copy link
Contributor

@Bhavya-egov Bhavya-egov commented Jan 6, 2025

Summary by CodeRabbit

  • Style
    • Updated health UI CSS stylesheet from version 0.2.4 to 0.2.5 in two project index.html files
    • Ensures latest styling is applied to the health UI component

@Bhavya-egov Bhavya-egov requested a review from a team as a code owner January 6, 2025 11:39
Copy link
Contributor

coderabbitai bot commented Jan 6, 2025

📝 Walkthrough

Walkthrough

This pull request involves updating the CSS stylesheet version for the health UI component across two HTML files. The changes increment the version of the @egovernments/digit-ui-health-css package from 0.2.4 to 0.2.5 in both health/micro-ui/web/micro-ui-internals/example/public/index.html and health/micro-ui/web/public/index.html. This update likely includes minor updates or fixes to the health UI styling.

Changes

File Change Summary
health/micro-ui/.../example/public/index.html Updated CSS stylesheet link version from 0.2.4 to 0.2.5
health/micro-ui/web/public/index.html Updated CSS stylesheet link version from 0.2.4 to 0.2.5

Possibly related PRs

Suggested reviewers

  • nipunarora-eGov
  • Swathi-eGov

Poem

🐰 A stylesheet hop, version so bright
CSS dancing with digital might
From 0.2.4 to 0.2.5 we leap
Health UI's style, no detail too deep
A rabbit's update, clean and light! 🎨


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.

@jagankumar-egov jagankumar-egov changed the title BUGFIX/HCMPRE-965 : Incremented css version BUGFIX/HCMPRE-965 : Incremented css version Jan 6, 2025
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

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f0e3c2f and 16a6cc9.

⛔ Files ignored due to path filters (1)
  • health/micro-ui/web/micro-ui-internals/packages/css/package.json is excluded by !**/*.json
📒 Files selected for processing (2)
  • health/micro-ui/web/micro-ui-internals/example/public/index.html (1 hunks)
  • health/micro-ui/web/public/index.html (1 hunks)
🔇 Additional comments (2)
health/micro-ui/web/micro-ui-internals/example/public/index.html (1)

15-15: LGTM! Version update is consistent.

The CSS version update from 0.2.4 to 0.2.5 aligns with the PR objective.

health/micro-ui/web/public/index.html (1)

13-13: LGTM! Version update is consistent across files.

The CSS version update to 0.2.5 matches the change in the other file, maintaining consistency throughout the application.

Let's verify no other files still reference the old version:

✅ Verification successful

✓ Version update is complete and consistent

The version update to 0.2.5 has been properly implemented across all relevant files in the codebase. No instances of the old version (0.2.4) remain.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any remaining references to the old CSS version
rg -l "[email protected]" --type html

Length of output: 45


Script:

#!/bin/bash
# Search for any CSS version references more broadly
echo "=== Searching for old version (0.2.4) ==="
rg "digit-ui-health-css.*0\.2\.4"

echo -e "\n=== Searching for new version (0.2.5) ==="
rg "digit-ui-health-css.*0\.2\.5"

echo -e "\n=== Searching for any other versions ==="
rg "digit-ui-health-css@[0-9]+\.[0-9]+\.[0-9]+" --only-matching

Length of output: 988

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