Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Namespace clash in generated handler

Offen
  • Stimmt etwas nicht?
#2,586 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
67/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
aws, csharp
Bereich
backend

Rechercherichtung

Start by locating the source generator that emits <Class>_<Method>_Generated.g.cs for Amazon.Lambda.Annotations and inspect how it writes parameter type names. Reproduce the namespace clash with the attached AnnotationsNamespaceClash.zip sample and run dotnet build; done when generated code uses globally qualified names and the sample builds without CS0234.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug needs-triage
Describe the bug

Generated handler doesn't use global:: for type names: build fails with CS0234 when a sibling namespace shadows the root namespace

The generated handler (<Class>_<Method>_Generated.g.cs) refers to parameter types by their
namespace-qualified name without a global:: prefix. The generated class is declared inside the handler's own
namespace, so if a namespace with the same first segment exists alongside it, C# name lookup stops at that
namespace and never reaches the top-level one. The result is CS0234 in generated code that the user cannot edit.

Regression Issue
  • Select this option if this issue appears to be a regression.
Expected Behavior

Generated code compiles regardless of which other namespaces exist. Emitting fully qualified global:: names for
every type in the generated file avoids the problem. The generator already emits some types with full names
(Amazon.Lambda.Core.ILambdaContext, Amazon.Lambda.SQSEvents.SQSEvent); they are only safe because nobody has an
Acme.Amazon namespace. The same bug applies to any root namespace.

Current Behavior

Build fails with error: error CS0234: The type or namespace name 'Lambda' does not exist in the namespace 'Acme.Common' (are you missing an assembly reference?)

The generated class is in namespace Acme.EventDistributor.Trigger. Resolving Common there searches
Acme.EventDistributor.Trigger, Acme.EventDistributor, Acme, and only then the global namespace. It finds
Acme.Common and stops, so Common.Lambda is looked up inside Acme.Common and fails.

In general, with a handler in A.B.C and a [FromServices] type in X.Y, the build breaks if A.X or A.B.X
exists without a matching Y below it.

Reproduction Steps

Run dotnet build for attached sample project AnnotationsNamespaceClash.zip

Possible Solution

Update source generator to emit fully qualified global:: names for all types referenced in generated code.

Additional Information/Context

No response

AWS .NET SDK and/or Package version used

Amazon.Lambda.Annotations v 2.4.1

Targeted .NET Platform

.NET SDK 10.0.401, net10.0

Operating System and version

Windows 11

Vorherrschende Sprache
C#
Sterne
1.7k
Forks
505
Ø Merge
1 T. 6 Std.
Gemergte PRs (30 T.)
10

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus aws/aws-lambda-dotnet

Alle Issues in aws/aws-lambda-dotnet

Ähnliche Issues

Weitere Issues zu C#

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.