fix: edit on github button issue resolved

[abdulbasithqb]

• I have followed the Your First Code Contribution section of the Contributing guide

Summarize the changes made and the motivation behind them.

Changes:
Corrected GitHub source href to ensure proper linking and functionality

Reference related issues using # followed by the issue number.

If there are breaking API changes - like adding or removing props, or changing the structure of the theme - describe them, and provide steps to update existing code.

Summary by CodeRabbit

• Bug Fixes
  • Updated the "Edit on GitHub" button to point to the correct URL path within the repository.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
flowbite-react	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 26, 2024 10:24am

[coderabbitai]

Walkthrough

The change involves updating the URL path for the EditOnGithubButton component, ensuring that users are directed to the correct location in the repository when they wish to edit or view the source code. This adjustment enhances the navigational experience and encourages community contributions by providing a direct and accurate link to the source files.

Changes

Files	Change Summary
.../code-demo.tsx	Updated githubSrcHref to a new URL path.

Poem

In the code's vast, open field, 🌱
A path was wrong, and now it's healed. 🛤️
With a hop, skip, and a jump, 🐰
The rabbit fixed the link, no slump.
Now contributors, far and wide, 🌍
Can edit with pride, side by side. ✨

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-tests 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 tests 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 tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[SutuSebastian]

Formatting

[SutuSebastian]

nice catch!

[coderabbitai]

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 8c1e992 and 31879be.

Files selected for processing (1)

• apps/web/components/code-demo.tsx (1 hunks)

Additional comments: 1

apps/web/components/code-demo.tsx (1)

• 226-226: The URL in the EditOnGithubButton component has been updated to point to a different path within the repository. This change directly addresses the PR's objective to correct the "Edit on GitHub" button's functionality. Ensure that the new URL path correctly leads to the intended section of the GitHub repository for editing. It might be beneficial to verify this by manually checking the constructed URL for a few different githubSlug values.

[abdulbasithqb]

Formatting

done

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 31879be and 948ceee.

Files selected for processing (1)

• apps/web/components/code-demo.tsx (1 hunks)

Additional comments: 2

apps/web/components/code-demo.tsx (2)

• 226-226: The githubSrcHref has been updated to point to a different URL path within the repository, addressing the issue with the "Edit on GitHub" button functionality. This change is crucial for ensuring users can navigate seamlessly to the specified section of the codebase from the button. However, it's important to verify that the new URL path is correct and accessible.
• 223-229: > 📝 NOTE

This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [208-208]

The class name code-preview used in the CodePreview component is flagged as not being a Tailwind CSS class. This might lead to styling issues or unintended appearance of the component. Consider verifying if this is a custom class defined elsewhere in the project's stylesheets or if it should be replaced with a valid Tailwind CSS class.