Skip to content

feat: Add associate knowledge functionality

Edouard Legoupil requested to merge associate-knowledge into main_dev

Created by: Edouard-Legoupil

This commit introduces the "Associate Knowledge" feature, which allows users to associate knowledge cards with a proposal.

  • Adds an "Associate Knowledge" button to the chat interface.

  • The button opens a modal that displays a list of knowledge cards filtered by the current context (donor, outcome, and field context).

  • Users can select knowledge cards from the modal.

  • The generated_sections of the selected cards are added to the user's prompt.

  • Adds a "Create New Knowledge Card" button to the modal.

  • Updates the backend API to support filtering knowledge cards.

  • 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