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

Stepper tag update #74

Merged
merged 2 commits into from
May 30, 2024
Merged

Stepper tag update #74

merged 2 commits into from
May 30, 2024

Conversation

Swathi-eGov
Copy link
Contributor

No description provided.

Copy link
Contributor

coderabbitai bot commented May 30, 2024

Walkthrough

The updates span multiple files in a React project, focusing on CSS styling adjustments, component enhancements, and documentation updates. Key changes include styling modifications for various components, the introduction of new props, and updates to version references in documentation and HTML files.

Changes

File Path Change Summary
react/css/README.md Updated tag and stepper styles in version 1.8.2-coreui.22.
react/css/src/digitv2/components/buttonsV2.scss Changed h2 element within the &:active state to set font-weight to theme(digitv2.fontWeight.bold).
react/css/src/digitv2/components/infoCardV2.scss Replaced h2 with .digit-infobanner-header for different alert types; added new styling rules for .individualElement h2 in .additional-elements-inline and .additional-elements-column.
react/css/src/digitv2/components/tagV2.scss Adjusted height and width properties based on aspect ratios for tablets and mobile devices; typography adjustments for different screen sizes.
react/example/public/index.html Updated CSS stylesheet link to version 1.8.2-coreui.22.
react/ui-components/README.md Added new prop activeSteps in the Stepper component in version 0.0.1-beta.31.
react/ui-components/src/atoms/InfoCard.js Added headerClassName prop to customize the header's CSS class.
react/ui-components/src/atoms/Stepper.js Included new dependencies (useState, useEffect), managed activeSteps state, and adjusted logic related to step activation.
react/ui-components/src/hoc/stories/Stepper.stories.js Added activeSteps prop to storybook controls and used it in the WithIsActive story.

Poem

In the land of code where changes flow,
Updates come and features grow.
Styles refined and props anew,
Step by step, the components flew.
With activeSteps and headers bright,
Our UI shines with pure delight.
🌟✨


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

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: CHILL

Commits

Files that changed from the base of the PR and between 76e334d and 844bf85.

Files ignored due to path filters (7)
  • react/css/package.json is excluded by !**/*.json
  • react/example/package.json is excluded by !**/*.json
  • react/modules/Project/package.json is excluded by !**/*.json
  • react/modules/core/package.json is excluded by !**/*.json
  • react/modules/sample/package.json is excluded by !**/*.json
  • react/package.json is excluded by !**/*.json
  • react/ui-components/package.json is excluded by !**/*.json
Files selected for processing (9)
  • react/css/README.md (1 hunks)
  • react/css/src/digitv2/components/buttonsV2.scss (1 hunks)
  • react/css/src/digitv2/components/infoCardV2.scss (6 hunks)
  • react/css/src/digitv2/components/tagV2.scss (4 hunks)
  • react/example/public/index.html (1 hunks)
  • react/ui-components/README.md (1 hunks)
  • react/ui-components/src/atoms/InfoCard.js (2 hunks)
  • react/ui-components/src/atoms/Stepper.js (7 hunks)
  • react/ui-components/src/hoc/stories/Stepper.stories.js (2 hunks)
Files skipped from review due to trivial changes (1)
  • react/example/public/index.html
Additional context used
Biome
react/ui-components/src/hoc/stories/Stepper.stories.js

[error] 12-12: This property value named props is later overwritten by an object member with the same name.

react/ui-components/src/atoms/InfoCard.js

[error] 35-35: Avoid using the index of an array as key property in an element.

react/ui-components/src/atoms/Stepper.js

[error] 72-80: Enforce to have the onClick mouse event with the onKeyUp, the onKeyDown, or the onKeyPress keyboard event.


[error] 111-115: JSX elements without children should be marked as self-closing. In JSX, it is valid for any element to be self-closing.


[error] 48-48: This hook specifies more dependencies than necessary: activeSteps


[error] 75-75: Avoid using the index of an array as key property in an element.

LanguageTool
react/css/README.md

[uncategorized] ~20-~20: A comma might be missing here.
Context: ...it UI's ``` ## Usage After adding the dependency make sure you have this dependency in ...


[grammar] ~93-~93: This phrase is duplicated. You should probably use “DIGIT Core” only once.
Context: ...ishnakole-wtt-egov] ## Published from DIGIT Core Digit Core Repo (https://github.com/egovernments/D...

react/ui-components/README.md

[uncategorized] ~18-~18: Possible missing comma found.
Context: ...ssion's ``` ## Usage After adding the dependency make sure you have this dependency in ...

Markdownlint
react/css/README.md

91-91: Expected: 0 or 2; Actual: 1
Trailing spaces


93-93: Expected: 0 or 2; Actual: 1
Trailing spaces


42-42: Expected: 1; Actual: 0; Above
Headings should be surrounded by blank lines


89-89: Expected: 1; Actual: 0; Above
Headings should be surrounded by blank lines


93-93: Expected: 1; Actual: 0; Below
Headings should be surrounded by blank lines


41-41: null
Fenced code blocks should be surrounded by blank lines


88-88: null
Fenced code blocks should be surrounded by blank lines


94-94: null
Bare URL used


98-98: null
Files should end with a single newline character

react/ui-components/README.md

43-43: Expected: 0 or 2; Actual: 1
Trailing spaces


97-97: Expected: 0 or 2; Actual: 1
Trailing spaces


57-57: Expected: 1; Actual: 2
Multiple consecutive blank lines


106-106: Expected: 1; Actual: 2
Multiple consecutive blank lines


107-107: Expected: 1; Actual: 3
Multiple consecutive blank lines


127-127: Expected: 1; Actual: 2
Multiple consecutive blank lines


146-146: Expected: 1; Actual: 2
Multiple consecutive blank lines


42-42: Expected: 1; Actual: 0; Below
Headings should be surrounded by blank lines


100-100: null
Fenced code blocks should be surrounded by blank lines


114-114: null
Fenced code blocks should be surrounded by blank lines


118-118: null
Fenced code blocks should be surrounded by blank lines


120-120: null
Fenced code blocks should be surrounded by blank lines


130-130: null
Bare URL used


138-138: null
Bare URL used

Additional comments not posted (12)
react/ui-components/src/hoc/stories/Stepper.stories.js (1)

61-75: The addition of activeSteps to commonArgs and its usage in the WithIsActive story correctly demonstrates the new functionality.

react/ui-components/src/atoms/InfoCard.js (1)

Line range hint 6-29: The addition of headerClassName enhances styling flexibility for the InfoCard component's header.

react/css/README.md (1)

45-45: The changelog update clearly documents the recent style updates, aiding in version tracking and user awareness.

react/ui-components/src/atoms/Stepper.js (3)

Line range hint 1-16: The direct import of useState and useEffect and the addition of activeSteps enhance the component's functionality and code clarity.


48-50: The new useEffect hook correctly handles changes in activeSteps, ensuring dynamic behavior of the stepper.


Line range hint 86-113: Adjustments in rendering logic based on activeSteps are correctly implemented, providing clear visual feedback on stepper progress.

react/css/src/digitv2/components/infoCardV2.scss (3)

24-24: Updates to the .digit-infobanner-header class enhance styling consistency and readability.


Line range hint 61-81: Addition of specific color styles for success, warning, and error variants enhances visual distinction and user experience.


Line range hint 116-135: Updates to the .individualElement h2 within .additional-elements-inline and .additional-elements-column classes ensure consistent styling across different layouts.

react/css/src/digitv2/components/tagV2.scss (1)

Line range hint 38-101: Updates to the .digit-tag class and its children enhance responsiveness and visual consistency across different devices.

react/ui-components/README.md (1)

61-61: Added documentation for the new activeSteps prop in the Stepper component.

This update is crucial for developers to understand the new capabilities of the Stepper component. It's well-documented in the changelog, which is essential for tracking the evolution of the component's features.

react/css/src/digitv2/components/buttonsV2.scss (1)

239-244: Updated the font-weight for the h2 element within the &:active state to theme(digitv2.fontWeight.bold).

This change ensures that the h2 text within active buttons is more prominent, aligning with the visual design requirements for active states. It's a good use of theming to maintain consistency across different components.

@jagankumar-egov jagankumar-egov merged commit e1115bd into develop May 30, 2024
1 check passed
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