Skip to content

feat(mobile-expo): RelatedQuestionsRenderer section component#326

Open
up-tandem wants to merge 1 commit intomainfrom
feat/311-related-questions-renderer
Open

feat(mobile-expo): RelatedQuestionsRenderer section component#326
up-tandem wants to merge 1 commit intomainfrom
feat/311-related-questions-renderer

Conversation

@up-tandem
Copy link
Contributor

Summary

  • Replaces the RelatedQuestions stub with an accordion-style FAQ renderer
  • Heading text above a list of expandable question rows
  • Each question is a tappable Pressable that toggles answer visibility (only one expanded at a time)
  • Chevron indicator (▸/▾) for expand/collapse state
  • Accessible: accessibilityState={{ expanded }} on each item
  • Empty questions array handled gracefully
  • Adds @babel/runtime dev dependency (required for components using React hooks with jest-expo)

Contracts Changed

No

Regeneration Required

No

Validation

  • pnpm --filter @forge/expo lint — passes with 0 warnings
  • pnpm --filter @forge/expo test -- --testPathPattern=RelatedQuestionsRenderer — 4/4 tests pass
  • pnpm --filter @forge/expo test -- --testPathPattern=SectionDispatcher — 11/11 tests pass (no regressions)

Resolves #311

🤖 Generated with Claude Code

Replace the RelatedQuestions stub with an accordion-style FAQ renderer.
Each question is a tappable row that toggles answer visibility with only
one expanded at a time. Add @babel/runtime dev dependency needed for
components using React hooks.

Resolves #311

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@coderabbitai
Copy link

coderabbitai bot commented Mar 10, 2026

Warning

Rate limit exceeded

@up-tandem has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 0 minutes and 44 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e1ba6493-54fe-443e-957b-60e7c33c34d7

📥 Commits

Reviewing files that changed from the base of the PR and between 2bc0bcd and d43db88.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (6)
  • mobile/expo/package.json
  • mobile/expo/src/components/sections/RelatedQuestionsRenderer.test.tsx
  • mobile/expo/src/components/sections/RelatedQuestionsRenderer.tsx
  • mobile/expo/src/components/sections/RelatedQuestionsStub.tsx
  • mobile/expo/src/components/sections/SectionDispatcher.tsx
  • mobile/expo/src/components/sections/index.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/311-related-questions-renderer

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

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

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.

feat(mobile-expo): RelatedQuestionsRenderer section component

1 participant