Skip to content

fix: Save new knowledge card before adding reference

Edouard Legoupil requested to merge fix-knowledge-card-reference-bug into main_dev

Created by: Edouard-Legoupil

When adding a reference to a new knowledge card that has not been saved yet, the application would fail because there was no ID to associate the reference with. This change modifies the handleSaveReference function to first check for a card ID. If one does not exist, it saves the card to the backend to retrieve an ID, then proceeds to save the reference. Only after the reference is successfully saved will the application navigate to the new card's URL. This ensures that references can be added to new cards seamlessly and avoids race conditions. Additionally, error handling has been improved to display more specific messages from the backend.

  • 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