refactor: mark props as readonly in multiple frontend components

[ThetaLogN]

Resolves #3418

This PR refactors 7 components to ensure that properties are marked as read-only.

Changes applied to:

• GlobalError
• UserDetailsLayout
• ProjectsLayout
• LogoCarousel
• MarkdownWrapper
• NavDropDown
• Providers

Checklist

• Required: I followed the contributing workflow
• Required: I verified that my code works as intended and resolves the issue as described
• Required: I ran make check-test locally: all warnings addressed, tests passed
• I used AI for code, documentation, tests, or communication related to this PR

[coderabbitai]

Summary by CodeRabbit

• Refactor
  • Enhanced type safety across React components by enforcing immutability constraints on component props at the type level. No changes to user-facing functionality or behavior.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Walkthrough

Wraps props type annotations with Readonly<> across seven frontend React components, changing parameter types to immutable Readonly-wrapped objects. No runtime logic or control-flow changes.

Changes

Cohort / File(s)	Summary
App layout components frontend/src/app/global-error.tsx, frontend/src/app/members/[memberKey]/layout.tsx, frontend/src/app/projects/layout.tsx	Component prop parameter types changed to Readonly<...> (e.g., { error: Error } → Readonly<{ error: Error }>).
UI components frontend/src/components/LogoCarousel.tsx, frontend/src/components/MarkdownWrapper.tsx, frontend/src/components/NavDropDown.tsx	Props parameter types updated to Readonly<...> for MovingLogos, Markdown, and NavDropdown.
Provider wrapper frontend/src/wrappers/provider.tsx	Providers component props updated to Readonly<{ children: React.ReactNode }>.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• refactor: mark BoardCandidatesLayout props as read-only #3409: Applies the same Readonly<> refactor pattern to React component props across other layout and component files.

Suggested reviewers

• kasya

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 12.50% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: marking props as readonly in multiple frontend components, which is the primary objective of the changeset.
Description check	✅ Passed	The description is clearly related to the changeset, specifying the issue resolved, the components affected, and confirming the author followed the contributing workflow and ran tests.
Linked Issues check	✅ Passed	The PR successfully addresses issue #3418 by applying Readonly type wrapping to props in all seven specified components: GlobalError, UserDetailsLayout, ProjectsLayout, LogoCarousel, MarkdownWrapper, NavDropDown, and Providers.
Out of Scope Changes check	✅ Passed	All changes are within scope—only type annotations wrapping props with Readonly are modified across the specified seven components, with no unrelated logic or functionality alterations.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud