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

Scripting

-

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)

  1. shanewarner123

    Jul 09, 2020 10:13

    The post is written in very a good manner and it contains many useful information for me thnku soo mchh..

    <a href="https://bettersafenow.com/">whole sale mask</a>

  2. sophiehahalala

    Jul 08, 2020 02:52

    Positive site, where did u come up with the information on this posting? I'm pleased I discovered it though, ill be checking back soon to find out what additional posts you include. Please visit our site https://www.titovid.com/

  3. Sofiakaif

    Jul 07, 2020 10:29

  4. Sofiakaif

    Jul 07, 2020 10:27

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.