[WEB-2134] chore: modify cycle options

[rahulramesha]

This PR modifies the cycle options to provide with the choice of not displaying the No cycle option

Summary by CodeRabbit

• New Features

  • Introduced a new property, canRemoveCycle, to enhance the functionality of the CycleDropdown and CycleOptions components, allowing users to conditionally remove cycles from the dropdown options.

• Improvements

  • Enhanced rendering logic in the CycleOptions component to provide context-sensitive options based on the canRemoveCycle property, improving user experience.

[coderabbitai]

Important

Review skipped

Auto reviews are limited to specific labels.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The changes enhance the CycleOptions and CycleDropdown components by introducing a new boolean property, canRemoveCycle. This property modifies the rendering behavior of the dropdown, allowing users to dynamically see or hide the "No cycle" option based on whether cycles can be removed. These adjustments improve user experience by providing more context-sensitive functionality without altering the core behavior of the components.

Changes

File	Change Summary
web/core/components/dropdowns/cycle/...	Added canRemoveCycle boolean property to CycleOptionsProps and Props in CycleDropdown, modifying rendering logic for dynamic control of options.

Poem

In a garden bright, where options bloom,
A cycle dances, banishing gloom.
With a flick of the prop, to add or not,
The rabbit hops in, giving it a shot!
"No cycle!" it sings, if the path is clear,
Enhancing our choices, spreading good cheer! 🐇✨

---

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f9e7a58 and abbe858.

Files selected for processing (2)

• web/core/components/dropdowns/cycle/cycle-options.tsx (2 hunks)
• web/core/components/dropdowns/cycle/index.tsx (3 hunks)

Additional comments not posted (5)

web/core/components/dropdowns/cycle/index.tsx (2)

28-28: LGTM! The new canRemoveCycle property is well-integrated.

The addition of the new optional property canRemoveCycle to the Props type is clear and aligns with the PR objectives.

---

50-50: LGTM! Ensure proper usage in CycleOptions.

The canRemoveCycle property is correctly integrated into the CycleDropdown component and passed to the CycleOptions component.

Verify that the canRemoveCycle property is correctly utilized in the CycleOptions component.

web/core/components/dropdowns/cycle/cycle-options.tsx (3)

32-32: LGTM! The new canRemoveCycle property is well-integrated.

The addition of the new property canRemoveCycle to the CycleOptionsProps type is clear and aligns with the PR objectives.

---

36-36: LGTM! The canRemoveCycle property is correctly integrated.

The canRemoveCycle property is correctly integrated into the CycleOptions component and utilized to conditionally modify the rendering behavior.

---

97-108: LGTM! The conditional logic for canRemoveCycle is well-implemented.

The conditional logic for rendering the "No cycle" option based on the canRemoveCycle property is well-implemented and enhances the component's functionality.