Announcement

Collapse
No announcement yet.

Inconsistent namespace ordering in "Reflectable" output

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

    Inconsistent namespace ordering in "Reflectable" output

    I am having an issue with the metadata output produced using the "Reflectable" attribute. It looks like my own code's metadata is output using one order of namespaces, then metadata from other assemblies re-declares the same variable using a different ordering of namespaces, as seen in the (very truncated) example below.
        var $m = Bridge.setMetadata,
            $n = ["Bridge.QUnit","System"];
        $m("GavinGreig.Test.ParameterValidationTest", function ()...
    
        var $m = Bridge.setMetadata,
            $n = ["System","Bridge.QUnit"];
        $m("Bridge.QUnit.Assert", function ()....
    This results in script errors over very basic things such as a C# method returning void. It seems to me that this is a bug in the behaviour of Reflectable; that the $m variable should only be declared once, and the order of namespaces in $n should not be subject to change.

    The output above was generated with reflection/disabled set to true in bridge.json and the following assembly attribute defined in C#:
    [assembly: Bridge.Reflectable("Bridge.QUnit.*")]
Working...
X