Fix: Slugify knowledge card download filename
Created by: Edouard-Legoupil
-
Slugify the filename of the downloaded knowledge card word document.
-
The filename is now generated from the card's title and summary.
-
The filename is generated on the backend and sent to the frontend via the Content-Disposition header.
-
The frontend now uses the filename from the Content-Disposition header.
-
This also fixes the download functionality for proposals.
-
This also fixes the failing frontend 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?