Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.1
Issue ID
1213506
Regression
No
ApiUpdater may leave orphan usings when only type qualified references were present in the source
In some scenarios after ApiUpdater runs old, non existing namespaces may be left in using clauses.
This may happen if Unity changes a type to a namespace that already exists and is already imported in the script.
For instance, consider the following:
// In UnityEngine.dll
namespace UnityEngine.Foo
{
class Bar {}
class Baz {} // Originally in UnityEngine.Other
}
// in user code
using UnityEngine.Foo;
using UnityEngine.Other;
class C : UnityEngine.Other.Baz
{
}
When ApiUpdater finishes updating user code it will looks something like:
// in user code
using UnityEngine.Foo;
using UnityEngine.Other; // Should have been removed
class C : Baz
{
}
Comments (63)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity Cloud icon does not appear next to project and does not connect correctly when the project is created with Cloud but closed right after creation
- ScrollerSlider in the Scroller Control is still using UXMLTraits
- Crash on ExtractHandles when shutting down the Editor in a specific scene while Burst jobs are in progress
- Unity Hub closes with no "Project is currently open" window when selecting an already open project from the Projects list
- The Hub freezes indefinitely when copy/pasting a lot of characters in the “Set project display name” Hub window since it has no character limit
sovojacket
Apr 14, 2021 16:02
Thanks