Added Chrome extension button

[Bashamega]

Fixes Issue

closes #147

Changes proposed

Check List (Check all the applicable boxes)

• My code follows the code style of this project.
• My change requires changes to the documentation.
• I have updated the documentation accordingly.
• All new and existing tests passed.
• This PR does not contain plagiarized content.
• The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Summary by CodeRabbit

• New Features
  • Introduced a new navigation item for "Download Browser Extension" in the SideNav component, enhancing user accessibility.
• User Interface Improvements
  • Updated the SideNav to include an icon for the new navigation item, improving visual appeal and user interaction.

[coderabbitai]

Walkthrough

The changes to the SideNav component add a new navigation item for downloading a browser extension. This enhancement improves user access to the extension, aligning with the user experience objectives outlined in the linked issue. The overall structure of the component remains unchanged, ensuring existing functionality is preserved while expanding user options.

Changes

File	Change Summary
src/components/SideNav.js	Added new navigation item "Download Browser Extension" with properties including name, href, current, external, and icon. Enhanced user interaction without altering existing functionalities.

Assessment against linked issues

Objective	Addressed	Explanation
Add a button to install the browser extension (##147)	✅

🐇 In the sidebar, a button now gleams,
For downloading extensions, fulfilling dreams.
A puzzle piece icon, shining bright,
Click it and soar, like a rabbit in flight!
Hopping through code, with joy we embrace,
Enhancing the web, a better place! 🥕

---

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 9a9ed7c and 59e9c1f.

Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (1)

• src/components/SideNav.js (2 hunks)

Additional comments not posted (2)

src/components/SideNav.js (2)

13-13: Import statement for PuzzlePieceIcon is correct.

The import statement aligns with the project's style guidelines and correctly imports the PuzzlePieceIcon.

---

86-93: New navigation item for downloading the browser extension is well-structured.

The new navigation item follows the pattern of existing items and correctly uses the PuzzlePieceIcon. The href points to the correct URL.

[eddiejaoude]

Looks great 👍

But please remove the lock file changes from your PR, these are not needed as there were no changes to the package file

[eddiejaoude]

Looks great 👍 thank you