Skip to content

refactor(crew): Refactor reference identification crew and fix API ke…

Edouard Legoupil requested to merge refactor-reference-crew into main_dev

Created by: Edouard-Legoupil

…y handling

This change refactors the reference identification crew to use the class-based @CrewBase structure, aligning it with the style of other crews in the project. This also resolves the pydantic validation error.

This change also fixes the Serper API key handling by centralizing it in the main config file. This resolves the 403 Forbidden error.

The crew's output is now logged to the main application log file.

  • 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