[MMU-UI] Replace native alert() with confirmationService in AppHeaderComponent

[lakxy]

app-header.component.ts already injects ConfirmationService but uses the native browser alert() 4 times for language-related errors.
This breaks UI consistency. Every other component uses the Angular Material dialog-based confirmation service.

[amanvaibhav162]

Hello @lakxy Sir,

Proposal: Replace alert() with ConfirmationService in App Header

I’d like to work on improving UI consistency in app-header.component.ts by replacing the usage of native alert() with the already injected ConfirmationService.

🔍 Issue Understanding
ConfirmationService is already available but not utilized
Native alert() is used for language-related errors
This creates inconsistency with the rest of the app, which uses Angular Material dialogs
🔧 Proposed Fix
Replace all alert() calls with ConfirmationService dialog methods
Ensure consistent styling and behavior across the application
Optionally standardize messages for better UX
🚀 Plan
Refactor the 4 alert usages to dialog-based confirmations
Test UI flow to ensure proper dialog handling
Align with existing dialog patterns used in other components

This will improve user experience and maintain consistency across the application UI.

[lakxy]

Hello @lakxy Sir,

Proposal: Replace alert() with ConfirmationService in App Header

I’d like to work on improving UI consistency in app-header.component.ts by replacing the usage of native alert() with the already injected ConfirmationService.

🔍 Issue Understanding ConfirmationService is already available but not utilized Native alert() is used for language-related errors This creates inconsistency with the rest of the app, which uses Angular Material dialogs 🔧 Proposed Fix Replace all alert() calls with ConfirmationService dialog methods Ensure consistent styling and behavior across the application Optionally standardize messages for better UX 🚀 Plan Refactor the 4 alert usages to dialog-based confirmations Test UI flow to ensure proper dialog handling Align with existing dialog patterns used in other components

This will improve user experience and maintain consistency across the application UI.

It has been fixed by the linked PR.