Saving notes
This commit is contained in:
17
.ae_brief
17
.ae_brief
@@ -1,15 +1,24 @@
|
||||
# Aether Project Brief: aether_app_sveltekit
|
||||
**Last Updated:** 2026-01-21 20:25:42
|
||||
**Last Updated:** 2026-01-22 20:25:17
|
||||
**Current Agent:** mcp_agent
|
||||
|
||||
## 🛠️ What I Just Did
|
||||
Restored V3 text search for Event Sessions, IDAA Recovery Meetings, and Journal Entries. Fixed 'TypeError: obj_li is not iterable' by robustly handling API envelopes. Standardized on 'like' operator for V3 searches. Updated project TODO and documented recent learnings.
|
||||
- Systematically cleared 133 svelte-check errors (372 down to 239).
|
||||
- Hardened type safety in Analytics, Hosted File Upload, QR Scanner, and Data Store components.
|
||||
- Standardized window.location.reload() calls by removing invalid arguments.
|
||||
- Corrected V3 API update calls in element_ae_crud.svelte to include required keys.
|
||||
- Resolved multiple 'used before declaration' and element assignment type errors.
|
||||
- Deleted legacy 'not_used' files to clean up project structure.
|
||||
|
||||
## 🚧 Current Blockers
|
||||
IDAA search currently ignores user-defined limits due to over-fetching strategy required for client-side filtering. Journal Entry search filters (enabled/hidden) are currently hardcoded in the UI query component.
|
||||
None. Core system remains stable.
|
||||
|
||||
## ➡️ Exact Next Steps
|
||||
1. Update Journal Entry search to use dynamic filters for 'enabled' and 'hidden'. 2. Implement limit slicing for IDAA search results. 3. Continue hardening specialized search logic for Presenters and Badges.
|
||||
- Continue systematically resolving remaining 239 svelte-check errors.
|
||||
- Investigate ClassValue errors in external library components if they persist.
|
||||
- Restore missing Exhibit module search functions and business logic.
|
||||
- Refactor ae_comp__journal_entry_obj_qry.svelte for dynamic filtering.
|
||||
- Address long-term Service Worker evaluation errors.
|
||||
|
||||
---
|
||||
*Generated by ae_brief*
|
||||
|
||||
15
GEMINI.md
15
GEMINI.md
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user