Giveth / giveth-dapps-v2

This project is the aggregation of GIVeconomy and Giveth.io DApps in a single repo
https://staging.giveth.io
GNU General Public License v3.0
54 stars 32 forks source link

add feedback form to footer and navbar #4355

Closed divine-comedian closed 1 day ago

divine-comedian commented 3 days ago

Summary by CodeRabbit

vercel[bot] commented 3 days ago

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

Name Status Preview Comments Updated (UTC)
giveth-dapps-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 28, 2024 5:47pm
coderabbitai[bot] commented 3 days ago

Walkthrough

The update introduces a new label for feedback in multiple languages and integrates corresponding feedback links into the user interface. Specifically, it enhances user interaction by adding feedback links to the footer section and community items menu.

Changes

Files Change Summary
lang/ca.json, lang/en.json, lang/es.json Added a new label label.tell_us_how_we_are_doing for user feedback in Catalan, English, and Spanish.
src/components/Footer/Footer.tsx Included a new anchor element in the footer for a "Leave Feedback" link.
src/components/menu/CommunityItems.tsx Added a community item for feedback, modifying link behavior to open in a new tab.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Footer
    participant CommunityItems
    participant FeedbackPage

    User->>Footer: Visits webpage
    Footer->>User: Displays "Leave Feedback" link
    User->>CommunityItems: Navigates to Community Menu
    CommunityItems->>User: Displays feedback link in menu
    User->>FeedbackPage: Clicks feedback link (opens in new tab)
    FeedbackPage->>User: Shows feedback form

Poem

In the footer, a link so bright,
"Leave Feedback" shines in the night.
Catalan, Spanish, English, too,
Inviting words, so fresh and new.
Click away, your voice we seek,
In the space where feedback speaks.
🌟✨


Recent review details **Configuration used: CodeRabbit UI** **Review profile: CHILL**
Commits Files that changed from the base of the PR and between 3a85dfd04c1da3afb900b7d580a4efbc9d4fb4f3 and aa4c3dcd3b462014891816fa789504afb709e176.
Files selected for processing (5) * lang/ca.json (1 hunks) * lang/en.json (1 hunks) * lang/es.json (1 hunks) * src/components/Footer/Footer.tsx (1 hunks) * src/components/menu/CommunityItems.tsx (2 hunks)
Files skipped from review due to trivial changes (1) * lang/es.json
Additional comments not posted (5)
src/components/menu/CommunityItems.tsx (2)
`33-37`: **New community item for feedback added.** The addition of a new community item for feedback is consistent with the PR objectives. The use of the `links.FEEDBACK` constant for the `href` attribute ensures that the link is maintained centrally, which is good for maintainability. --- `43-58`: **Conditional rendering logic for the new feedback link.** The conditional rendering logic correctly differentiates the feedback link to open in a new tab (`target='_blank'` with `rel='noreferrer noopener'`). This is a good security practice for links leading to external sites, ensuring that no referrer information is passed and that the new page cannot control the original page.
src/components/Footer/Footer.tsx (1)
`125-135`: **New feedback link added in the footer.** The addition of the "Leave Feedback" link in the footer is well-implemented. The use of `target='_blank'` and `rel='noreferrer noopener'` for the anchor tag is a good practice for external links, ensuring security and proper behavior. The use of `formatMessage` with the `id` 'label.leave_feedback' aligns with the internationalization practices of the rest of the application. [APROVED]
lang/en.json (1)
`980-980`: **New label addition confirmed and correctly implemented.** The JSON key `label.tell_us_how_we_are_doing` has been added successfully with the value "Tell us how we're doing", which aligns with the PR's objectives to solicit user feedback. The syntax is correct, and the key naming convention is consistent with other labels in the file.
lang/ca.json (1)
`980-980`: **Addition of New Label for User Feedback** The new label `label.tell_us_how_we_are_doing` has been added correctly. This label is likely used to prompt users for feedback, which is a good enhancement for improving user engagement and collecting valuable user insights. The translation "Explica'ns com ho estem fent" seems appropriate for Catalan.
--- 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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `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 Configration 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.