Skip to content

Fix discourse complement direction overlap bug (#292)#322

Open
salmonumbrella wants to merge 1 commit intoRoamJS:mainfrom
salmonumbrella:pr/issue-292
Open

Fix discourse complement direction overlap bug (#292)#322
salmonumbrella wants to merge 1 commit intoRoamJS:mainfrom
salmonumbrella:pr/issue-292

Conversation

@salmonumbrella
Copy link

@salmonumbrella salmonumbrella commented Feb 15, 2026

Fixes #292

  • What changed: Reworked discourse relation matching to evaluate forward/backward direction independently and emit both when overlap is valid.
  • Why this fixes it: complement-direction overlap cases no longer drop or misclassify matching relations.

@coderabbitai
Copy link

coderabbitai bot commented Feb 15, 2026

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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.

Discourse Context query error when source/destination and label/complement are the same

1 participant