Skip to content

fix: Correct reference ingestion and re-ingestion logic

Edouard Legoupil requested to merge feature-enhance-reference-ingestion-revised into main_dev

Created by: Edouard-Legoupil

This commit fixes a bug where the referenceId was being passed as [object Object] to the API endpoint, causing a 422 Unprocessable Entity error.

It also correctly implements the re-ingestion logic to force force_scrape=True when a single reference is re-ingested.

  • The onClick handler for the "Ingest References" button has been corrected to prevent passing an event object.

  • The handleIngestReferences function now includes a more robust check to differentiate between bulk and single ingestion.

  • The backend endpoint for re-ingestion now correctly forces scraping.

  • 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