feat: add cookies policy page and footer link#692
Conversation
✅ Deploy Preview for astounding-nougat-da0f6a ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
@ArshiBansal is attempting to deploy a commit to the adityapaul2603-gmailcom's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Review limit reached
More reviews will be available in 54 minutes and 4 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughA new ChangesCookie Policy Page and Footer Integration
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related issues
Possibly related PRs
🚥 Pre-merge checks | ✅ 6 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (6 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/components/cookiespage.jsx`:
- Line 280: The JSX text content on line 280 in cookiespage.jsx contains an
unescaped double quote character within the string "version will be posted here
with a new "Last updated" date." which triggers the react/no-unescaped-entities
lint rule. Replace the unescaped double quote characters around "Last updated"
with the HTML entity " to properly escape them in JSX text content.
In `@src/components/Footer.jsx`:
- Line 184: The cookies link route in the Footer component is using
`/cookiespage` but the application's route contract defines the cookies page
route as `/cookies`. Update the `to` prop in the cookies link (currently set to
`/cookiespage`) to match the correct route contract by changing it to
`/cookies`.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yml
Review profile: CHILL
Plan: Pro Plus
Run ID: fcc91db0-c786-4e79-b6b6-0704930d70cd
📒 Files selected for processing (2)
src/components/Footer.jsxsrc/components/cookiespage.jsx
| <p> | ||
| We may update this policy from time to time to reflect | ||
| changes in our practices or for legal reasons. The updated | ||
| version will be posted here with a new "Last updated" date. |
There was a problem hiding this comment.
Resolve JSX unescaped quote lint error.
Line 280 contains unescaped " in JSX text (react/no-unescaped-entities), which can fail lint checks.
Suggested fix
- version will be posted here with a new "Last updated" date.
+ version will be posted here with a new "Last updated" date.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| version will be posted here with a new "Last updated" date. | |
| version will be posted here with a new "Last updated" date. |
🧰 Tools
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/components/cookiespage.jsx` at line 280, The JSX text content on line 280
in cookiespage.jsx contains an unescaped double quote character within the
string "version will be posted here with a new "Last updated" date." which
triggers the react/no-unescaped-entities lint rule. Replace the unescaped double
quote characters around "Last updated" with the HTML entity " to properly
escape them in JSX text content.
Source: Linters/SAST tools
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
2 participants
Pull Request Summary
feat: add cookies policy page and footer link
What changed?
CookiesPage.jsxwith a comprehensive, professional Cookie Policy.Footer.jsxto include a "Cookies" link next to the "About Project" link./cookiesroute-ready page with proper sections covering all required legal details.Main files affected:
src/pages/CookiesPage.jsx(new)src/components/Footer.jsx(updated)Why is this needed?
This fulfills legal and transparency requirements by providing users with clear information about cookie usage on AlgoScope. It also improves user trust and completes the site's footer navigation.
Closes #675
Type of Change
feat- New user-facing feature or algorithm capabilityfix- Bug fix or regression fixdocs- Documentation-only changestyle- Formatting or styling change with no behavior changerefactor- Code restructuring with no feature or bug-fix behavior changeperf- Performance improvementtest- Test coverage or test infrastructure changebuild- Build system, dependency, or packaging changeci- GitHub Actions, Docker, Vercel, or release automation changechore- Maintenance change that does not affect usersrevert- Reverts a previous changeRelease Notes
Release note category:
Release note entry:
Testing and Verification
npm ciornpm installnpm run format:checknpm run lintnpm run buildhttp://localhost:5173Skipped or additional testing notes:
Tested navigation from footer to
/cookiesand all internal anchor links.UI Evidence
Before:
(No Cookies page or link in footer)
After:
(Screenshots/GIFs would be attached in actual PR)
CI/CD and Deployment Impact
Deployment notes:
Remember to add the route
<Route path="/cookies" element={<CookiesPage />} />in your router configuration (App.jsx / main routing file).Reviewer Checklist
Summary by CodeRabbit
Release Notes