fix(milestone): [milestone] repair component sample document

[chenxi-20]

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• [ ] The commit message follows our Commit Message Guidelines
• [ ] Tests for the changes have been added (for bug fixes / features)
• [ ] Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• [ ] Bugfix
• [ ] Feature
• [ ] Code style update (formatting, local variables)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] CI related changes
• [ ] Documentation content changes
• [ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• [ ] Yes
• [ ] No

Other information

Summary by CodeRabbit

• New Features

  • Enhanced visual representation of milestone status with updated styling and color coding.
  • Introduced a new CSS class .status for improved layout behavior of status displays.

• Bug Fixes

  • Updated color representation for the completed status across multiple components to ensure consistency in design.

• Tests

  • Adjusted test scripts to reflect updated color values for visual elements, ensuring accurate validation of styles.

• Documentation

  • No changes to documentation were made in this release.

[coderabbitai[bot]]

[!CAUTION]

Review failed

The pull request is closed.

Walkthrough

The changes primarily involve updates to the statusMap object across multiple Vue component files, specifically altering the color representation for the completed status. Additionally, modifications to the template and style sections include the introduction of a new CSS class .status in some components, enhancing the visual representation of milestone statuses. The overall structure and functionality of the components remain unchanged, focusing on visual styling adjustments.

Changes

File Path	Change Summary
.../milestone/custom-bottom-top-composition-api.vue	Updated <span> class to include status, modified statusMap for completed color, added .status CSS class.
.../milestone/custom-bottom-top.vue	Updated <span> class to include status, modified statusMap for completed color, added .status CSS class.
.../milestone/custom-flag-composition-api.vue	Modified statusMap for completed color.
.../milestone/custom-flag.vue	Modified statusMap for completed color.
.../milestone/data-field-mapping-composition-api.vue	Modified statusMap for completed color.
.../milestone/data-field-mapping.vue	Modified statusMap for completed color.
.../milestone/flag-before-composition-api.vue	Modified statusMap for completed and other status colors.
.../milestone/flag-before.vue	Modified statusMap for completed and other status colors.
.../milestone/milestone-events-composition-api.vue	Modified statusMap for completed color.
.../milestone/milestone-events.vue	Modified statusMap for completed color.
.../milestone/show-number-composition-api.vue	Modified statusMap for completed color.
.../milestone/show-number.vue	Modified statusMap for completed color.
.../milestone/solid-style-composition-api.vue	Modified statusMap for completed color.
.../milestone/solid-style.vue	Modified statusMap for completed color.
.../milestone/flag-before.spec.ts	Updated test case color values for flagAfterLineColors and flagBeforeLineColors.
.../milestone/show-number.spec.ts	Updated color value in iconStyles for visual representation of milestone nodes in tests.
.../milestone/solid-style.spec.ts	Updated expected CSS properties for icon styles in the test.

Possibly related PRs

• #2152: The changes in the main PR regarding the statusMap variable and CSS class .status are related to the same variables and classes modified in this PR, indicating a shared focus on visual representation and styling.
• #2193: This PR also modifies the statusMap variable, specifically the completed key, aligning with the changes made in the main PR.
• #2196: The updates to the statusMap variable in the main PR are relevant to the changes in this PR, which also involves modifications to the same variable.
• #2233: The changes in the main PR regarding the statusMap variable are related to the updates made in this PR, which also modifies the same variable.
• #2241: The modifications to the statusMap variable in the main PR are relevant to the changes in this PR, which also involves updates to the same variable.
• #2381: The changes in the main PR regarding the statusMap variable are directly related to the updates made in this PR, which also modifies the same variable.
• #2400: The changes in the main PR regarding the statusMap variable are relevant to the updates made in this PR, which also involves modifications to the same variable.
• #2407: The modifications to the statusMap variable in the main PR are related to the changes in this PR, which also involves updates to the same variable.
• #2411: The changes in the main PR regarding the statusMap variable are relevant to the updates made in this PR, which also modifies the same variable.
• #2417: The modifications to the statusMap variable in the main PR are related to the changes in this PR, which also involves updates to the same variable.
• #2425: The changes in the main PR regarding the statusMap variable are relevant to the updates made in this PR, which also modifies the same variable.
• #2444: The modifications to the statusMap variable in the main PR are related to the changes in this PR, which also involves updates to the same variable.
• #2445: The changes in the main PR regarding the statusMap variable are relevant to the updates made in this PR, which also modifies the same variable.
• #2454: The modifications to the statusMap variable in the main PR are related to the changes in this PR, which also involves updates to the same variable.
• #2459: The changes in the main PR regarding the statusMap variable are relevant to the updates made in this PR, which also modifies the same variable.

Suggested labels

documentation

Suggested reviewers

• zzcr

🐰 In the meadow, colors bright,
Status changes, a lovely sight.
From active hues to shades anew,
Milestones shine, fresh and true.
With classes added, styles in play,
Hopping forward, come what may! 🌼

---

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.