Warn at codegen time about conflicting names in xmlns
- Dominant language
- C#
- Stars
- 23.3k
- Forks
- 2k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 296
Description
### Description
When there's a conflicting names in a XAML xmlns, the inflators used to pick the First() (but with ordering undefined). #29579 makes the inflation fail, at runtime or XamlC time.
We should be proactive and report a diagnostic warning at the time the code behind for the xaml (xmalg) is generated, so the issue can be reported in the IDE
### Public API Changes
none
### Intended Use-Case
/
Contributor guide
Research direction
Start by reading #29579 and tracing the XAML code-generation path that produces the xmalg code-behind, then examine how conflicting names in an xmlns are detected. Confirm the existing runtime and XamlC failure behavior; done means generation emits a diagnostic warning for the conflict so it can be reported in the IDE instead of silently selecting First().
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100