- Shipped
- September 17, 2026 at 5:48 PM UTC
- Author
- Kamo
- Commit
- 7a18185
It called /api/webinar/leads/{id}, which MediaService never served (live 404), and a 404 reads to this section as "the feature is off" — so it rendered nothing, silently, for a lead whose demo booking was sitting in the database. It now reads GET **************** (securityservice 82cee28), which serves it under the lead's own read gate. The TypeScript mirrored a DTO the server never sent, the same drift MyWebinarsTab had: scheduledDate and presenterName did not exist. LeadWebinarEntry mirrors the Java record, dates and times go through useFormatters in the member's zone, and the status chip is the server's label rather than four English strings restated here. A lead who cancelled shows Cancelled, not the session's Scheduled — they are not attending a webinar that is still going ahead. A 403 (not your lead to read) leaves the section hidden, like an empty list; only a real failure shows the error line. LeadWebinarsSection.test.tsx covers all three from the server's payload shape: all fail against the previous component. tsc clean, eslint clean on the touched files, npm test guards pass.