This commit fixes a bug where presentations, presenters, and files related to a session were not being displayed. The issues were caused by incorrect property names ( suffix) and improper use of Svelte 5 features after a recent refactoring.
This commit introduces a major refactoring of the data processing logic across multiple modules (events, archives, posts, sponsorships) to use a standardized pattern with . This improves consistency and maintainability.
Key changes:
- Replaced module-specific data processing with a generic helper.
- Removed deprecated functions.
- Updated Svelte components to leverage the new Svelte 5 runes, simplifying state management.
- Fixed linting errors and updated test configurations.
- Added .
This commit fixes a bug where the session view was not displaying correctly due to incorrect usage of reactive props.
- In , the prefix was added to the props passed to the component to make them reactive.
- In , the prefix was removed from the variables in the template, as they are already reactive when using Svelte 5 runes.
- The block for was corrected to use the resolved value.
This commit fixes a bug where presentations were not being displayed correctly within the event session view. The issue was caused by an incorrect query that was using the standard session ID to filter presentations, instead of the random session ID.
The liveQuery in has been updated to use the from the derived variable. This ensures that the query correctly fetches all presentations associated with the session.
Reverted changes to legacy launcher links in various components. These links are intentionally structured to work with nginx location aliases and should not be modified to conform to SvelteKit routing.
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 introduces the initial setup for the `ae_app_3x_llm` branch.
The purpose of this branch is to explore and implement more direct
collaboration with AI Large Language Models (LLMs) for complex code
changes, including the creation of new function libraries and the
modification of existing code.
This initial commit includes:
- GEMINI.md: A file to provide context to the AI about the project.
- TODO.md: A to-do list for upcoming development tasks, created in
collaboration with the AI.