From b10851c209a33d21de60b0ebdf1fc03188c5d85e Mon Sep 17 00:00:00 2001 From: woikos Date: Wed, 14 Jan 2026 18:18:31 +0100 Subject: [PATCH] fix: add frontend-compatible aliases in getcuratingconfig response The frontend expected 'categories' and 'custom_kinds' but the backend returned 'kind_categories' and 'allowed_kinds'. Add aliases for both naming conventions to ensure frontend compatibility. Co-Authored-By: Claude Opus 4.5 --- app/handle-nip86-curating.go | 3 +++ 1 file changed, 3 insertions(+) diff --git a/app/handle-nip86-curating.go b/app/handle-nip86-curating.go index a047449..70572e7 100644 --- a/app/handle-nip86-curating.go +++ b/app/handle-nip86-curating.go @@ -444,8 +444,11 @@ func (s *Server) handleGetCuratingConfig(dbACL *database.CuratingACL) NIP86Respo "first_ban_hours": config.FirstBanHours, "second_ban_hours": config.SecondBanHours, "allowed_kinds": config.AllowedKinds, + "custom_kinds": config.AllowedKinds, // Alias for frontend compatibility "allowed_ranges": config.AllowedRanges, + "kind_ranges": config.AllowedRanges, // Alias for frontend compatibility "kind_categories": config.KindCategories, + "categories": config.KindCategories, // Alias for frontend compatibility "config_event_id": config.ConfigEventID, "config_pubkey": config.ConfigPubkey, "configured_at": config.ConfiguredAt,