Progress value fixed

[GoldGroove06]

Gave a definite value of 45% to the progress bar. Removed random value fixing issue #585

Summary by CodeRabbit

• New Features
  • Simplified the Progress component story by removing dynamic behavior, now using static values from props.
• Bug Fixes
  • Eliminated the random value generation for the progress indicator, ensuring consistent display based on provided arguments.

[coderabbitai]

Walkthrough

The changes in this pull request involve the Progress component's story located in Progress.stories.js. The local state management for the value prop has been removed, along with the getRandomValue function and the useEffect hook that updated the value dynamically. The component now receives its props directly through the args parameter, resulting in a static representation of the progress value.

Changes

File Path	Change Summary
src/components/ui/Progress/stories/Progress.stories.js	Removed local state management for value prop, eliminated getRandomValue function, and removed useEffect hook.

Possibly related issues

• BUG: Remove random progress value for the Progress component to avoid flaky visual snapshot tests #585: This change addresses the issue of removing random progress values for the Progress component to avoid flaky visual snapshot tests, aligning with the goal of making the behavior static.

Suggested reviewers

• kotAPI

Poem

🐇 In the meadow where progress flows,
A static tale now gently grows.
No more random leaps to sway,
Just steady steps in a bright array.
Hooray for changes, clear and bright,
Our progress shines with all its might! 🌟

---

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

🧹 Outside diff range and nitpick comments (2)

src/components/ui/Progress/stories/Progress.stories.js (2)

Line range hint 23-27: Consider adding more stories for different progress states

While the 45% progress story is good, consider adding additional stories to showcase:

• Empty progress (0%)
• Full progress (100%)
• Edge cases (e.g., near-full at 99%)

Example addition:

export const Empty = {
    args: {
        ...All.args,
        value: 0
    }
};

export const Full = {
    args: {
        ...All.args,
        value: 100
    }
};

🧰 Tools

🪛 eslint

[error] 9-12: Block must not be padded by blank lines.

(padded-blocks)

---

[error] 11-12: More than 1 blank line not allowed.

(no-multiple-empty-lines)

---

[error] 20-21: More than 1 blank line not allowed.

(no-multiple-empty-lines)

---

11-12: Remove extra blank line

ESLint detected multiple consecutive blank lines. Remove one blank line to comply with the project's formatting rules.

🧰 Tools

🪛 eslint

[error] 9-12: Block must not be padded by blank lines.

(padded-blocks)

---

[error] 11-12: More than 1 blank line not allowed.

(no-multiple-empty-lines)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between f9a21a0 and b9c89aa.

📒 Files selected for processing (1)

• src/components/ui/Progress/stories/Progress.stories.js (1 hunks)

🧰 Additional context used

🪛 eslint

src/components/ui/Progress/stories/Progress.stories.js

[error] 11-12: More than 1 blank line not allowed.

(no-multiple-empty-lines)

🔇 Additional comments (1)

src/components/ui/Progress/stories/Progress.stories.js (1)

10-14: LGTM! Simplified story implementation

The removal of dynamic state management in favor of static props makes the story more predictable and better aligned with Storybook's purpose of showcasing component states.

🧰 Tools

🪛 eslint

[error] 11-12: More than 1 blank line not allowed.

(no-multiple-empty-lines)