Skip to content

feat: Enhance Knowledge Card feature and update documentation

Edouard Legoupil requested to merge feature/knowledge-card-and-docs into main_dev

Created by: Edouard-Legoupil

This commit introduces several improvements to the Knowledge Card feature and updates the documentation to reflect all the recent changes.

Knowledge Card (screens/KnowledgeCard/KnowledgeCard.jsx):

  • The Knowledge Card display on the dashboard now shows an icon corresponding to the linked item (Donor, Outcome, or Field Context).
  • The form for creating and editing Knowledge Cards has been updated:
    • The "Reference Type" field is now a compulsory dropdown menu at the top of the form.
    • A "Geographic Coverage" dropdown now appears when "Field Context" is selected, which filters the available items.
    • The buttons have been restyled and realigned for better usability.
  • The "Save Card" button now navigates the user back to the "Knowledge Card" tab on the dashboard after a successful save.

Backend (api/proposals.py):

  • The /field-contexts endpoint has been updated to allow filtering by geographic_coverage.

Documentation:

  • The frontend/README.md and backend/README.md files have been updated to document all the new features and API endpoints that have been added.

Testing:

  • A new Playwright test file (frontend/tests/new_features.spec.js) has been added to cover the new features.

  • The test data (frontend/tests/test-data.sql) has been updated to support the new tests.

  • 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