KamoCRM

Fetch member/org data directly instead of through hooks

Fixkamo-internal
Shiked
18 Mart 2026 19:53 UTC
Yazar
kamo
Yap
cb64f5c

Removed useUserInfo, useSignatureData, and useImageResolver hooks which each had independent async fetch cycles causing race conditions where memberId/orgId were 0 during initial renders. Now fetches data in a single sequential flow: 1. GET /api/user-info to get memberID + orgID from session 2. Parallel fetch GET /api/security/members/{id} + GET /api/security/org/{id} 3. Resolve image URLs from theme path 4. Build content state with all real data This matches how other tool window components load data — direct fetch calls with credentials, no intermediate hook dependencies.

Tüm değişiklikler

Kargoyu gördüğünüz gibi?

Tüm bunlar kendi başına iş alanınıza geliyor. Ücretsiz plana başlayın ve bu sayfayı bir ay içinde tekrar okuyun.

Sonsuza Kadar Ücretsiz BaşlangıçFırsatları Görüntüle