Scott.Idem/OSIT-AE-App-Svelte
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Saving notes

Browse Source
This commit is contained in:
Scott Idem
2026-01-22 20:25:33 -05:00
parent a8e9c39ac6
commit 6925229d56
2 changed files with 28 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
GEMINI.md
View File

@@ -61,6 +61,21 @@ This project is the frontend UI/UX for the Aether (AE) system, built with Svelte
## 📝 Development History (Consolidated)
### Hardening & Error Reduction Sprint (2026-01-22)
- **Error Reduction:** Systematically cleared ~133 `svelte-check` errors (from 372 to 239) across the entire application.
- **Type Hardening:**
- `analytics.svelte`: Moved global `Window` interface declarations to a dedicated module script block to resolve ambient module errors.
- `element_ae_crud.svelte`: Hardened types for `patch_result` and corrected `core_func.update_ae_obj_id_crud` calls to include required `key` property.
- `element_codemirror_editor.svelte`: Added null checks and type casting for `editor_container` element assignment.
- `element_data_store.svelte`: Resolved "used before declaration" errors by correctly sequencing props destructuring and variable initialization.
- `AE_AITools.svelte`: Added robust fallbacks for optional `model` and `systemPrompt` properties.
- `ae_sponsorships_functions.ts`: Fixed imports and aligned V3 API calls with consistent `fields` pattern.
- **Cleanup & Standards:**
- Removed redundant `true` argument from `window.location.reload()` calls across several components (`e_app_cfg`, `e_app_help_tech`).
- Resolved `onsubmit` type mismatches in `ae_comp__hosted_files_upload.svelte` by transitioning to generic `Event` with internal casting.
- Hardened QR Scanner and File Table elements with proper parameter typing and element casting.
- Deleted multiple legacy/unused files (prefixed with `not_used`).
### Hardening & Search Restoration (2026-01-21)
- **Critical Learning: V3 Search Body Strictness:** The `search_query` POST body is extremely strict. Adding non-mapped fields (e.g., `event_location_name`) triggers HTTP 400 "Unauthorized search field" errors.
- **Critical Learning: Preservation of Business Logic:** Specialized search parameters (`ft_qry`, `lk_qry`, `and_qry`) are handled by custom backend logic and MUST be passed as URL query parameters (serialized JSON), not in the search body. These are the "sacred" rules of the Aether system and must not be "cleaned up" during modernization.