Skip to content

🐛 fix(config): sync usage service bootstrap after auto-load#92

Merged
seakee merged 1 commit into
mainfrom
fix/usage-service-bootstrap-sync
May 14, 2026
Merged

🐛 fix(config): sync usage service bootstrap after auto-load#92
seakee merged 1 commit into
mainfrom
fix/usage-service-bootstrap-sync

Conversation

@seakee
Copy link
Copy Markdown
Owner

@seakee seakee commented May 14, 2026

Summary

Fix a CPA panel state mismatch where auto-loading a valid external Usage Service configuration did not immediately expose Request Monitoring navigation.

Cause

The manager settings page updated only local page state after auto-load succeeded.
The shared Usage Service bootstrap store was refreshed only on explicit save.

Solution

  • Sync the external Usage Service bootstrap address into the shared store after successful auto-load
  • Keep normalization and deduplication in a focused helper
  • Add regression coverage for normalization and no-op sync cases

Testing

  • npm test -- src/pages/ConfigPage.test.ts

Sync the external Usage Service bootstrap address into the shared store after CPA panel config auto-load succeeds in the manager settings page.

This fixes the state mismatch where the config showed as loaded but the request monitoring menu stayed hidden until the user saved again.

Add a focused regression test for bootstrap sync normalization and deduplication. Low risk: the change only updates frontend bootstrap state.
@seakee seakee merged commit 1891e6c into main May 14, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant