Skip to content

fix: resolve multiple issues in chat and knowledge association

Edouard Legoupil requested to merge fix-knowledge-association-and-auth into main_dev

Created by: Edouard-Legoupil

This commit addresses several bugs and improves the user experience in the chat and knowledge card association features.

  • feat(auth): Extend session and token expiration to 8 hours to prevent intermittent 401 Unauthorized errors during long user sessions.

  • fix(chat): Gracefully handle 403 Forbidden errors when fetching proposal status history, preventing console errors for users without permission.

  • fix(accessibility): Add inputId to CreatableSelect components to correctly associate labels with form controls, improving accessibility.

  • feat(knowledge): Enhance the 'Associate Knowledge' modal to allow de-association of cards by enabling the confirm button when the selection changes.

  • fix(knowledge): Ensure the list of associated knowledge cards is correctly displayed in the chat component.

  • 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