style(frontend): apply prettier formatting to landing 3D files#67
Conversation
Run npm run format over the App, HeroExperience and LandingPage files from the 3D landing work (#64) that weren't formatted before merge. Whitespace / line-wrapping only — no logic or behavior changes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for docuthinker-ai-app ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
There was a problem hiding this comment.
Code Review
This pull request applies formatting and indentation adjustments to frontend/src/App.js and frontend/src/components/three/HeroExperience.js to improve code structure and readability. No functional changes were introduced, and there are no review comments to address.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Summary
Applies
npm run format(Prettier) to the three landing-page / 3D files from the full-page 3D landing work (#64) that weren't formatted before merge. Whitespace + line-wrapping only — no logic or behavior changes.frontend/src/App.jsfrontend/src/components/three/HeroExperience.jsfrontend/src/pages/LandingPage.jsTesting
npm run formatis now idempotent on these files (re-running produces no diff).jest→ 53 passed / 11 suites, 18 snapshots unchanged (confirms no render-level change).🤖 Generated with Claude Code