Skip to content

fix(frontend): Correct rendering logic and add fallback for old propo…

Edouard Legoupil requested to merge feature-chat-section-ordering-and-table-styling into main_dev

Created by: Edouard-Legoupil

…sals

This commit fixes a critical rendering bug in the Chat.jsx component.

The previous changes to enforce section ordering introduced a regression that broke rendering for both new and existing proposals. This was caused by incorrect variable access in the rendering loop.

This commit corrects the variable accessors for both the new template-based rendering logic and the fallback logic for older proposals. This ensures that both new and existing proposals will render correctly.

  • 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