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

fix: Arrow Buttons Visible at Carousel Start and End Positions #473

Merged

Conversation

SWITCHin2
Copy link

@SWITCHin2 SWITCHin2 commented Nov 9, 2024

Issue : #457
The "Prev" button is now conditionally rendered based on the active index. It will only appear if the active index is greater than 0 (i.e., not on the first item).
The "Next" button is conditionally rendered based on the active index. It will only appear if the active index is less than the last item (i.e., not on the last item).

Screenshots
Screenshot 2024-11-09 at 10 52 26 PM

Screenshot 2024-11-09 at 10 52 13 PM

Summary by CodeRabbit

  • New Features

    • Improved navigation in the Review Carousel by conditionally displaying "next" and "prev" buttons based on the active index, enhancing user experience.
  • Bug Fixes

    • Prevented users from navigating beyond the bounds of carousel items.

Copy link

vercel bot commented Nov 9, 2024

Someone is attempting to deploy a commit to the bunty's projects Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Nov 9, 2024

Walkthrough

The ReviewCarousel component has been updated to conditionally render navigation buttons based on the active index. The "next" button is now displayed only when the active index is less than the last item, and the "prev" button appears only when the active index is greater than zero. This prevents users from navigating beyond the available carousel items. The existing logic for item styling and automatic cycling remains unchanged, ensuring consistent visual presentation.

Changes

File Change Summary
frontend/src/components/ui/ReviewCarousel.jsx Conditional rendering of "next" and "prev" buttons based on the active index to prevent out-of-bounds navigation.

Possibly related PRs

Suggested labels

bug, level1, gssoc-ext, hacktoberfest accepted

Suggested reviewers

  • RamakrushnaBiswal

🐇 In a carousel, we spin and sway,
Buttons now hide when they're in the way.
With a click and a hop, we glide with glee,
Navigating our path, as smooth as can be!
Hooray for the changes, let's cheer and play! 🎉


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

Copy link
Contributor

github-actions bot commented Nov 9, 2024

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

@SWITCHin2
Copy link
Author

@RamakrushnaBiswal Can you please review and if this PR is well and good to merge, then merge it ASAP as tommorow is the last day for gssoc-ext

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

🧹 Outside diff range and nitpick comments (2)
frontend/src/components/ui/ReviewCarousel.jsx (2)

156-167: Enhance accessibility and mobile UX of the Next button.

While the conditional rendering logic is correct, consider these improvements:

  1. Add ARIA labels for screen readers
  2. Replace text arrows with semantic icons (e.g., using a UI icon library)
  3. Increase touch target size for mobile users
 {active < items.length - 1 && (
   <motion.button
     id="next"
+    aria-label="Next slide"
     className=" absolute top-[40%] text-green-900 bg-none border-none text-6xl font-mono font-bold opacity-80 transition-opacity z-10 right-[50px] max-sm:text-white max-sm:text-2xl max-sm:right-2"
     onClick={() =>
       setActive((prev) => (prev + 1 < items.length ? prev + 1 : prev))
     }
     whileHover={{ x: 10, color: '#00B2CA', opacity: 1 }}
   >
-    {'>>'}
+    <span className="max-sm:text-4xl">{'>'}</span>
   </motion.button>
 )}

168-178: Clean up Prev button implementation and improve accessibility.

Similar to the Next button, enhance accessibility and mobile experience. Also remove the unnecessary space character.

 {active > 0 && (
   <motion.button
     id="prev"
+    aria-label="Previous slide"
     className=" absolute top-[40%] text-green-900 bg-none border-none text-6xl font-mono font-bold opacity-80 transition-opacity z-10 left-[50px] max-sm:text-white max-sm:text-2xl max-sm:left-2"
     onClick={() => setActive((prev) => (prev - 1 >= 0 ? prev - 1 : prev))}
     whileHover={{ x: -10, color: '#00B2CA', opacity: 1 }}
   >
-    {' '}
-    {'<<'}
+    <span className="max-sm:text-4xl">{'<'}</span>
   </motion.button>
 )}
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ca6cdb3 and 7ffc83d.

📒 Files selected for processing (1)
  • frontend/src/components/ui/ReviewCarousel.jsx (1 hunks)
🔇 Additional comments (1)
frontend/src/components/ui/ReviewCarousel.jsx (1)

156-178: Consider improving auto-cycling behavior at carousel boundaries.

The current implementation might create a disconnect between button visibility and auto-cycling behavior. When the carousel reaches the last item (Next button hidden) or first item (Prev button hidden), the auto-cycling continues, which could be unexpected for users.

Consider these improvements:

  1. Pause auto-cycling when reaching the last item
  2. Add visual indicators for the current position (e.g., dots)
  3. Add a pause/play button for user control

Let's verify the auto-cycling behavior:

@RamakrushnaBiswal RamakrushnaBiswal merged commit 829c5d6 into RamakrushnaBiswal:main Nov 10, 2024
4 of 5 checks passed
@RamakrushnaBiswal RamakrushnaBiswal added bug Something isn't working level1 for 10 points gssoc-ext gssoc-extd program hacktoberfest accepted hacktoberfest-accepted repo labels Nov 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working gssoc-ext gssoc-extd program hacktoberfest accepted hacktoberfest-accepted repo level1 for 10 points
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants