Duplicate constants in `ClientAppMessages` that already exist in `SharedAppMessages`

[Cyrus-Sushiant]

The class ClientAppMessages defines three constants:

• NAVIGATE_TO
• PROFILE_UPDATED
• BACKGROUND_JOB_PROGRESS
  These same constants are already defined in the base class SharedAppMessages. Because of this duplication, the compiler emits warnings such as:

The keyword 'new' is required on 'NAVIGATE_TO' because it hides the constant 
'string Boilerplate.Shared.Infrastructure.Services.SharedAppMessages.NAVIGATE_TO'

Remove the duplicated constants from ClientAppMessages and rely on the inherited values from SharedAppMessages.

[yasmoradi]

That seems to be by design
Create a project with --signalr true and --signalr false and see the difference before starting @Cyrus-Sushiant

[Cyrus-Sushiant]

That seems to be by design
Create a project with --signalr true and --signalr false and see the difference before starting @Cyrus-Sushiant

Thanks for the clarification — I checked the generated projects with both --signalr true and --signalr false, and you're right: the duplication of constants is intentional for the SignalR-enabled template.

However, for NAVIGATE_TO specifically, there is no conditional check like the one used for PROFILE_UPDATED.
So even in the non‑SignalR scenario, NAVIGATE_TO is still duplicated in both ClientAppMessages and SharedAppMessages, which triggers the hiding warning.

I think we should add the same kind of if condition around NAVIGATE_TO (similar to PROFILE_UPDATED) or remove the duplicate to avoid unnecessary constant hiding.