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

Added the feedback form(both frontend and backend logic) #260

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

Praveenkumar5048
Copy link

Related Issue

This pull request is related to issue #234

Description

  1. The have Completed the implementation of feedback form.
  2. "Give Feedback" button in the footer section, clicking on this, feedback modal opens up,
    user gives their details and write feedback and also rate our app experiance on a scale of 5.
  3. This information is stored in the mongoDb
  4. I have added mongodb model for feedback, and also created route and controllers folders for handling http request from frontend.

Type of PR

  • Bug fix
  • [X ] Feature enhancement
  • Documentation update
  • Other (specify): _______________

Screenshots / videos (if applicable)

Screenshot 2024-06-17 123343

Screenshot 2024-06-17 110639

Checklist:

  • [ X] I have performed a self-review of my code
  • [X ] I have read and followed the Contribution Guidelines.
  • [X ] I have tested the changes thoroughly before submitting this pull request.
  • [ X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
  • [X ] I have commented my code, particularly in hard-to-understand areas.

Additional context:

I request the admin to please review my code and merge this PR. I am open to any suggestions or modifications
Thank you

Copy link

vercel bot commented Jun 17, 2024

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

Name Status Preview Comments Updated (UTC)
kaam-do ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 24, 2024 5:44pm

Copy link

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! 😊

@PatilHarshh
Copy link
Owner

conflicts

@Praveenkumar5048
Copy link
Author

@PatilHarshh I will recheck my code and try to resolve the conflicts

@Praveenkumar5048
Copy link
Author

@PatilHarshh i have resolved the conflicts and incorporated latest changes into my code from the main branch. I have created a new PR resolving these issues, please go through that and merge my PR.

Thank you

Copy link

gitguardian bot commented Jun 24, 2024

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
11775317 Triggered Generic High Entropy Secret 6aaa592 client/dist/assets/index-1f76e8ca.js View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@Praveenkumar5048
Copy link
Author

@PatilHarshh please review my code, it doesn't contains any merge conflicts, merge this PR

@Praveenkumar5048
Copy link
Author

@PatilHarshh PLEASE MERGE MY PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants