Libary not showing anything until pressing Search

[leifiyoo]

Only after I press Search on the Library on the server panel it shows some plugins. this is really annoying

[github-actions]

Issue Analysis

[BUG CONFIRMED]

---

Summary

This is a data initialization bug in the Library component. The plugins list is not being fetched/populated when the component initially mounts. Instead, data is only loaded when the user explicitly clicks the Search button, indicating a missing initial data fetch in the component's lifecycle.

---

Root Cause Analysis

Why This Occurs

Based on the described behavior, the issue points to one of these common patterns:

1. Missing for initial data fetch - The component likely has a search handler that fetches data, but no corresponding effect to load data on mount:

2. Conditional rendering based on search state - The UI might be conditionally hiding results until search is triggered:

3. Empty initial state with lazy loading - The state is initialized as empty and only populated through explicit user action.

---

Likely Location

Based on the project structure, the bug is likely in:

---

Suggested Fix

Option 1: Add Initial Fetch Effect

Option 2: If Using Custom Hook

Option 3: Fix Conditional Rendering

If the issue is conditional rendering:

---

Steps to Reproduce

1. Open the Catalyst application
2. Navigate to the server panel
3. Click on the Library tab/section
4. Observe: Empty list despite plugins being available
5. Click the Search button without entering any query
6. Observe: Plugins suddenly appear

---

Additional Recommendations

1. Add loading state - Show a loading indicator during initial fetch to improve UX
2. Handle empty state - If no plugins exist, show a helpful message instead of blank screen
3. Consider debounced search - Auto-search as user types with debounce, making explicit search button optional
4. Add error boundary - Gracefully handle fetch failures with retry option

---

Priority Assessment

Severity: Medium
Impact: Poor user experience, confusing interface
Effort: Low (simple useEffect addition)

This should be prioritized as it affects core functionality discoverability and makes the application appear broken to users.

[leifiyoo]

#13