Fix: Correctly load session content in new launcher

The session content was not loading in the new Events Launcher because the loaded session data was not being correctly assigned to the events store.

This commit fixes the issue by correctly assigning the loaded session object and its nested properties to the events store.
This commit is contained in:
Scott Idem
2025-11-13 19:03:43 -05:00
parent 0e960ba955
commit aef34dc79b

View File

@@ -110,10 +110,10 @@ function handle_load_ae_obj_id__event_session(event_session_id: any) {
.then(async (load_results) => {
console.log(`load_results = `, load_results);
$events_slct.event_session_obj = load_results.event_session_obj;
$events_slct.event_file_obj_li = load_results.event_file_obj_li;
$events_slct.event_presentation_obj_li = load_results.event_presentation_obj_li;
$events_slct.event_presenter_obj_li = load_results.event_presenter_obj_li;
$events_slct.event_session_obj = load_results;
$events_slct.event_file_obj_li = load_results.event_file_li;
$events_slct.event_presentation_obj_li = load_results.event_presentation_li;
// $events_slct.event_presenter_obj_li = load_results.event_presenter_obj_li;
// let new_url = data_url.toString();