Revert "Revert "Added feedback form and sitemap to the footer""
Reverts shravan20/github-readme-quotes#326
Summary by CodeRabbit
-
New Features
- Introduced a new footer component that includes a feedback form for user submissions.
- Added a success message component to confirm feedback submission.
- Enhanced environment configuration with new variables for form handling and contact information.
-
Dependencies
- Added new dependencies for improved form handling and environment variable management.
-
Bug Fixes
- Improved form validation to ensure all fields are completed before submission.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| github-readme-quotes | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Oct 15, 2024 10:23am |
| github-readme-quotes-returns | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Oct 15, 2024 10:23am |
Walkthrough
The pull request introduces several changes to the frontend of a React application. It adds new environment variables to the .env.example file, updates the package.json to include new dependencies for form handling and environment management, and introduces two new components: Footer and ResponseSuccess. The Footer component contains a feedback form and links, while ResponseSuccess displays a confirmation message upon successful form submission. The Footer component is also integrated into the Home component.
Changes
| File | Change Summary |
|---|---|
frontend/.env.example |
Added environment variables: REACT_APP_FORMSPREE_FORM_CODE, REACT_APP_GITHUB_REPO_URL, REACT_APP_CONTACT_EMAIL. |
frontend/package.json |
Added dependencies: @formspree/react (^2.5.1), dotenv (^16.4.5); added devDependency: dotenv-webpack (^8.1.0). Expanded browserslist section. |
frontend/src/components/Footer/Footer.js |
Introduced Footer component with a feedback form and essential links using Material-UI. |
frontend/src/components/Footer/ResponseSuccess.js |
Introduced ResponseSuccess component to display a success message after form submission. |
frontend/src/components/Pages/Home/index.js |
Integrated <Footer /> component into the Home component. |
Possibly related PRs
-
#323: This PR introduces the same environment variables in
frontend/.env.exampleand adds a feedback form in theFootercomponent, which is also part of the main PR.
Poem
In the footer, we gather,
With forms to share our chatter.
A success message bright,
Makes our feedback feel right.
Links to explore, oh what a delight,
In this app, everything's just right! 🐇✨
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?
🪧 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
@coderabbitaiin 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
@coderabbitaiin 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 pauseto pause the reviews on a PR. -
@coderabbitai resumeto resume the paused reviews. -
@coderabbitai reviewto trigger an incremental review. This is useful when automatic reviews are disabled for the repository. -
@coderabbitai full reviewto do a full review from scratch and review all the files again. -
@coderabbitai summaryto regenerate the summary of the PR. -
@coderabbitai resolveresolve all the CodeRabbit review comments. -
@coderabbitai configurationto show the current CodeRabbit configuration for the repository. -
@coderabbitai helpto get help.
Other keywords and placeholders
- Add
@coderabbitai ignoreanywhere in the PR description to prevent this PR from being reviewed. - Add
@coderabbitai summaryto generate the high-level summary at a specific location in the PR description. - Add
@coderabbitaianywhere in the PR title to generate the title automatically.
CodeRabbit Configuration File (.coderabbit.yaml)
- You can programmatically configure CodeRabbit by adding a
.coderabbit.yamlfile 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.
@RajatX24: You can consider this branch and check what is the issue? Else I will take a look at this during weekend as I am caught up now.
Thank you in advance!