Skip to content

🤔 [ISSUE] - Prioritize Blocks with the Most Matching NLU Entities #821

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
marrouchi opened this issue Mar 12, 2025 · 0 comments · May be fixed by #956
Closed

🤔 [ISSUE] - Prioritize Blocks with the Most Matching NLU Entities #821

marrouchi opened this issue Mar 12, 2025 · 0 comments · May be fixed by #956
Assignees

Comments

@marrouchi
Copy link
Contributor

marrouchi commented Mar 12, 2025

Description

Currently, blocks in Hexabot can be triggered by NLU entities (intent, keyword entity values, etc.). However, when multiple blocks match based on NLU entities, there is no clear prioritization strategy.

This feature request aims to prioritize the block with the highest number of matching NLU entities, ensuring that the most relevant block is triggered. Additionally, trait entities should have a higher priority over other types of entities.

Acceptance Criteria:

  • When multiple blocks match based on NLU entities, the block with the most matches should be triggered.
  • Trait entities should take priority over other entity types in determining the next block.
  • Ensure that the existing NLU-based block triggering mechanism remains functional.
  • Add unit tests to validate the prioritization logic.

To be ignored:

  • If multiple blocks have the same number of matching entities, fallback to an explicitly configured priority (if available).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment