Skip to content

Updated the Pydantic validator in `backend/api/knowledge.py` from `@v…

Edouard Legoupil requested to merge fix-warning into main_dev

Created by: Edouard-Legoupil

…alidator` to @field_validator and updated the import statement.

Replaced the deprecated ``@app.on_event("startup") with a `lifespan` context manager in `backend/main.py`.

Added websockets>=12.0 to backend/requirements.txt to address the websockets.legacy deprecation warning.

  • 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