🐛 Fix stale MCP token data after create/regenerate (#10280)

Fix the root cause in profile.cljs: remove the optimistic conj from
access-token-created and instead chain a fetch-access-tokens after the
create-access-token API call succeeds. This ensures all callers get a
fresh, server-consistent token list automatically.

Suggested-by: niwinz

Signed-off-by: kapilvus <kapil69265@gmail.com>
Co-authored-by: kapilvus <kapilvus@gmail.com>
This commit is contained in:
kapil971390 2026-06-18 14:56:50 +05:30 committed by GitHub
parent b573a71017
commit 11f3ef2549
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -495,9 +495,7 @@
(ptk/reify ::access-token-created
ptk/UpdateEvent
(update [_ state]
(-> state
(assoc :access-token-created access-token)
(update :access-tokens conj access-token)))))
(assoc state :access-token-created access-token))))
(defn create-access-token
[params]
@ -510,8 +508,10 @@
(meta params)]
(->> (rp/cmd! :create-access-token params)
(rx/map access-token-created)
(rx/tap on-success)
(rx/mapcat (fn [token]
(rx/of (access-token-created token)
(fetch-access-tokens))))
(rx/catch on-error))))))
;; --- EVENT: delete-access-token