ENG-1469: Refactor getDiscourseRelations and getDiscourseNodes to read from block props#853
Conversation
…d from block props
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |
📝 WalkthroughWalkthroughThis PR implements a feature-flagged migration of discourse nodes and relations retrieval from legacy configuration to a new settings-store-backed approach. The accessors are refactored to transform settings data into standardized DiscourseNode and DiscourseRelation types, the Condition type is exported publicly with a new "not or" variant, and consumer functions conditionally route to the new store or preserve existing behavior. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). 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 |
initSingleDiscourseNode was writing backedBy: "default" which caused nodes to be filtered out of the settings panel when the flag is ON. Also fixes up existing graphs that already stored the wrong value.
https://www.loom.com/share/c2ec64fca234492d9a0cd15f7a44a067
Summary by CodeRabbit
New Features
Refactoring