Skip to content

feat: Enhance Associate Knowledge functionality

Edouard Legoupil requested to merge feature/associate-knowledge-enhancements into main_dev

Created by: Edouard-Legoupil

This commit enhances the "Associate Knowledge" functionality by:

  1. Displaying the list of selected knowledge cards in a new box on the chat screen, providing clear visual feedback to the user.
  2. Passing the associated knowledge cards' content to the backend as structured data, rather than appending it to the user's prompt.
  3. Modifying the backend to dynamically create a knowledge base from the associated knowledge cards and inject it into the crewai agent responsible for proposal generation.

This ensures that the AI-generated content is more relevant and context-aware, based on the selected knowledge.

  • Does my code meet the quality standards for releasing packages?
  • Does the reviewer have all the information to validate the features/issues without too much research?
  • Does the customer who will validate the associated tickets have the information to do so without wasting time?

Issues to validate to close :

  • issue #

Processed issues to keep open or in progress:

  • issue #

Checklist:

  • Does the package check go local?
  • Does the CI pass?
  • Are the added / fixed features documented, tested?
  • Are the added features / solved problems briefly presented in the PR message?
  • Are the changes related to tickets / issues that I have listed in the commits and in the PR itself?
  • Are the tickets in "review" mode in the Project Tracking Board?
  • Does each ticket, if it is to be closed after acceptance of the PR, contain a comment that tells how to validate it?

Merge request reports