Better example in the section: Enable sensitive data logging

[ThomasSkyldahl]

Description

Wouldn't a better option be to use Environment.IsProduction() to avoid enabling sensitive logging in the production environment.
The current example shows the use of #if DEBUG to decide how the sensitive logging is handled.
this could lead to leaking sensitive information if somebody deploys a DEBUG assembly to production for any given reason.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/blazor/blazor-ef-core?view=aspnetcore-9.0

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/blazor-ef-core.md

Document ID

2ebc5e4d-bab4-6d30-9018-9a712c482236

Platform Id

5fb075cd-0c65-79c2-a4ad-4a4658816c3b

Article author

@guardrex

Metadata

• ID: 2ebc5e4d-bab4-6d30-9018-9a712c482236
• PlatformId: 5fb075cd-0c65-79c2-a4ad-4a4658816c3b
• Service: aspnet-core
• Sub-service: blazor

Related Issues

[github-actions]

🏖️🌞 Summertime!! Woot!! 🏐⛵

Stand-by! ... A green dinosaur 🦖 will be along shortly to assist.

[guardrex]

Hi @ThomasSkyldahl ... I think it came over from the product unit that way many years ago. I'll change it, and we'll see on review if they prefer to check the environment. However, we'll be checking for the Development environment. If devs want to change the logic to report in other environments (e.g., Staging), it will be easy enough for them to modify the conditional.

Stand-by ... I'll have this on a PR in a sec .................