Repository navigation
fix: faq dom nesting - #1348
fix: faq dom nesting#1348
Conversation
|
Warning: Component files have been updated but no migrations have been added. See https://github.com/yext/visual-editor/blob/main/packages/visual-editor/src/components/migrations/README.md for more information. |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe stylesheet adds an Priority: ⬇️ Low Change: Bug fix Merge Risk: ⚪ Minimal · up to This change fixes invalid DOM nesting in FAQ answers and adds a small-text variant for rich text. No concrete merge-blocking risk was found. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ 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 |
resolvedAnswer is an RTF so it's wrapped in dev, so it can't be passed to
<Body>which wraps in p. The variant is already applied by resolveComponentData, although we were missing the xs variant for RTF. I think this is the issue causing the minified react error from the bug bash.