Fix: Ensure IDAA Recovery Meetings respect the user-defined limit

- Simplified limit logic in search__event and qry_ae_obj_li__event_v2 to use the passed value directly.
- Added .slice(0, limit) to filtered results in Event module to handle over-fetching correctly.
- Explicitly passed the qry__limit from idaa_loc to the meeting list components.
- Applied .limit() to the Dexie liveQuery in the meeting list wrapper.
- Updated the UI result count and loop to strictly adhere to the requested limit.
This commit is contained in:
Scott Idem
2026-01-22 18:10:42 -05:00
parent 0ab6d2b3e3
commit 02132fc5e8
4 changed files with 11 additions and 8 deletions

View File

@@ -479,7 +479,7 @@ export async function search__event({
enabled,
hidden,
view,
limit: (qry_person_id || qry_conference !== null || qry_physical !== null || qry_virtual !== null || qry_type !== null) ? 500 : limit,
limit,
offset,
order_by_li,
log_lvl
@@ -495,7 +495,7 @@ export async function search__event({
enabled,
hidden,
view,
limit: (qry_person_id || qry_conference !== null || qry_physical !== null || qry_virtual !== null || qry_type !== null) ? 500 : limit,
limit,
offset,
order_by_li,
log_lvl
@@ -572,7 +572,7 @@ export async function search__event({
console.log(`Filter results (V3 Search): Input=${processed_obj_li.length}, Output=${filtered_obj_li.length}`);
}
return filtered_obj_li;
return filtered_obj_li.slice(0, limit);
}
export const qry_ae_obj_li__event = search__event;
@@ -637,7 +637,7 @@ export async function qry_ae_obj_li__event_v2({
for_obj_id,
enabled,
hidden,
limit: (qry_person_id || qry_conference !== null || qry_physical !== null || qry_virtual !== null || qry_type !== null) ? 500 : limit,
limit,
offset,
order_by_li,
params_json,
@@ -707,7 +707,7 @@ export async function qry_ae_obj_li__event_v2({
console.log(`Filter results (V2): Input=${processed_obj_li.length}, Output=${filtered_obj_li.length}`);
}
return filtered_obj_li;
return filtered_obj_li.slice(0, limit);
}
// Updated 2025-05-09