Fixed MarkDown formatting

This commit is contained in:
Scott Idem
2025-11-13 14:38:30 -05:00
parent 4d6c10cbad
commit 4b4c3c5552

18
TODO.md
View File

@@ -47,21 +47,21 @@ This is a list of tasks to be completed before the next event/show/conference.
These functions are frequently used and critical to the application's data flow. Reviewing and cleaning them up will significantly improve the codebase. These functions are frequently used and critical to the application's data flow. Reviewing and cleaning them up will significantly improve the codebase.
1. **`get_ae_obj_li_for_obj_id_crud_v2()`** (from `src/lib/ae_api/api_get__crud_obj_li_v2.ts`) 1. **`get_ae_obj_li_for_obj_id_crud_v2()`** (from `src/lib/ae_api/api_get__crud_obj_li_v2.ts`)
* **Why:** This is the main function for fetching lists of data from the backend, used extensively across all modules. - **Why:** This is the main function for fetching lists of data from the backend, used extensively across all modules.
* **Cleanup:** Review parameters and return types for consistency, improve error handling, and add more detailed logging for debugging. - **Cleanup:** Review parameters and return types for consistency, improve error handling, and add more detailed logging for debugging.
2. **`db_save_ae_obj_li__ae_obj()`** (from `src/lib/ae_core/core__idb_dexie.ts`) 2. **`db_save_ae_obj_li__ae_obj()`** (from `src/lib/ae_core/core__idb_dexie.ts`)
* **Why:** This function is the single point of entry for saving data to the local Dexie database, critical for performance and reliability. - **Why:** This function is the single point of entry for saving data to the local Dexie database, critical for performance and reliability.
* **Cleanup:** Optimize for bulk operations, add robust error handling and logging, and ensure correct handling of updates to existing objects. - **Cleanup:** Optimize for bulk operations, add robust error handling and logging, and ensure correct handling of updates to existing objects.
3. **The `process_ae_obj__*_props()` family of functions** (e.g., `process_ae_obj__journal_props()` from `src/lib/ae_journals/ae_journals__journal.ts`) 3. **The `process_ae_obj__*_props()` family of functions** (e.g., `process_ae_obj__journal_props()` from `src/lib/ae_journals/ae_journals__journal.ts`)
* **Why:** These functions transform API data for the frontend and are a common source of bugs and inconsistencies. - **Why:** These functions transform API data for the frontend and are a common source of bugs and inconsistencies.
* **Cleanup:** Standardize their structure across all modules, ensure they are pure functions, and add unit tests for correctness. - **Cleanup:** Standardize their structure across all modules, ensure they are pure functions, and add unit tests for correctness.
* **Update 2025-11-13 (Temporary Rollback):** The previous refactoring of these functions has been temporarily rolled back due to an `InternalError`. `ae_core_functions.ts` has been restored. The new plan is to refactor these functions module by module, ensuring stability at each step. The generic CRUD functions in `core__crud_generic.ts` were simplified to remove data processing and caching, delegating those responsibilities to the module-specific functions. The deprecated `process_ae_obj__props` function in that file was left in place but is no longer used by the generic CRUD functions. - **Update 2025-11-13 (Temporary Rollback):** The previous refactoring of these functions has been temporarily rolled back due to an `InternalError`. `ae_core_functions.ts` has been restored. The new plan is to refactor these functions module by module, ensuring stability at each step. The generic CRUD functions in `core__crud_generic.ts` were simplified to remove data processing and caching, delegating those responsibilities to the module-specific functions. The deprecated `process_ae_obj__props` function in that file was left in place but is no longer used by the generic CRUD functions.
4. **Usage of `liveQuery` from Dexie** 4. **Usage of `liveQuery` from Dexie**
* **Why:** `liveQuery` is powerful for reactive UIs, but current usage suggests complexity and potential issues. - **Why:** `liveQuery` is powerful for reactive UIs, but current usage suggests complexity and potential issues.
* **Cleanup:** Review `liveQuery` usage throughout the application, simplify queries, and investigate reactivity issues. Consider wrapping `liveQuery` in a custom Svelte store for a more predictable interface. - **Cleanup:** Review `liveQuery` usage throughout the application, simplify queries, and investigate reactivity issues. Consider wrapping `liveQuery` in a custom Svelte store for a more predictable interface.
--- ---