Search Issue Tracker
Fixed
Fixed in 6000.0.59f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1
Votes
0
Found in
6000.0.57f1
6000.2.4f1
6000.3.0a6
Issue ID
UUM-116673
Regression
No
Code generation fails to prefix the fully qualified reference with global:: when a property is tagged with [UxmlAttribute] or [UxmlObjectReference] that contains a similar namespace segment as the current class's namespace
Reproduction steps:
1. Open the attached project "ReproProj"
2. Check the Project window
3. Notice the folders called "MyLibrary.SomeLibrary.Extention" and "SomeLibrary"
4. Observe the Console
Expected result: No namespace Errors exist
Actual result: Namespace Errors like “Unity.UIToolkit.SourceGenerator\Unity.UIToolkit.SourceGenerator.UxmlSerializedDataGenerator\MyLibrary.SomeLibrary.Extension.UxmlObjectExample.gen.cs(27,62): error CS0234: The type or namespace name 'SomeClass' does not exist in the namespace 'MyLibrary.SomeLibrary“ are present
Reproducible with: 6000.0.57f1, 6000.2.4f1, 6000.3.0a6
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Animator state transition preview clips are flickering when zooming in
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- "DebugAllocatorMode" option changes when changed in another Editor instance
Add comment