Skip to content

This commit introduces a wide range of improvements to the codebase, …

Edouard Legoupil requested to merge improve-codebase-quality into refactor-backend

Created by: Edouard-Legoupil

…focusing on security, reliability, and maintainability.

Key changes include:

  • Hardened Dockerfile with a non-root user and other security best practices.

  • Secured backend configuration by removing hardcoded secrets and credentials.

  • Improved dependency management with pinned versions for both backend and frontend.

  • Enhanced document handling to use in-memory streaming instead of temporary files.

  • 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