You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
admin-ui: stop logging raw AxiosError (api-token) on list/delete failures #96
Follow-up from the #95 review (non-blocking P2), not a regression of that PR. The preset-save failure path added in #95 logs only a bounded message; this issue covers older admin-ui call sites that still log a raw AxiosError.
Verified facts
admin-ui/src/utils/request.js:68-70 adds the auth token to every request config:
The response interceptor already toasts a bounded message for these failures, so the raw console log adds no required signal and exposes the token (and potentially request data) in devtools or support screenshots.
Expected behavior
Failed list/delete requests must not log the raw AxiosError/config. Log only a bounded diagnostic (for example e?.message || String(e), consistent with reportCreateBuildFailure at index.vue:1116) or drop the log where the interceptor already surfaced the failure.
Acceptance
A failing custom_preset/list, custom_build/list, custom_preset/delete, or custom_build/delete request does not print config.headers['api-token'] or request bodies to the console.
A bounded diagnostic remains for genuinely unexpected failures (or the failure is already fully surfaced by the interceptor).
Activity
admin-ui: stop logging raw AxiosError on request failures (#97)