Recursive property setup overrides previous setups about moq4 HOT 7 CLOSED

For completeness the interfaces are defined as:

    public interface Foo
    {
        Bar Bar { get; }
    }

    public interface Bar
    {
        Baz Baz { get; }
        Qux Qux { get; }
    }

    public interface Qux
    {
        string Value { get; }
    }

    public interface Baz
    {
        string Value { get; }
    }

from moq4.

Seems like a valid use case and a bug :(

from moq4.

It gets awkward when you replace bar with

  var bar = new BarImpl {
    Baz = baz,
    Qux = qux
  }

If the recursive syntax ends on a mock it should still work.

I've solved my issue by writing a method that takes a Func<T, TMocked> to get an IMocked, and an Expression<Func<TMocked, TProperty>> to pass to SetupGet.

Do you want me to have a look at fixing this?

from moq4.

Would love it if you could give it a shot!

Thanks

/kzu

On Thu, May 15, 2014 at 3:27 PM, James Foster [email protected]:

It gets awkward when you replace bar with

var bar = new BarImpl {
Baz = baz,
Qux = qux
}

If the recursive syntax ends on a mock it should still work.

I've solved my issue by writing a method that takes a Func<T, TMocked> to
get an IMocked, and an Expression<Func<TMocked, TProperty>> to pass to
SetupGet.

Do you want me to have a look at fixing this?

Reply to this email directly or view it on GitHubhttps://github.com//issues/110#issuecomment-43246948
.

from moq4.

Cool. I'll check it out. I came across the relevant areas of the code when making my last pull request. Shouldn't be too difficult. (He says)

from moq4.

Closing this, this problem will be tracked in #643 (together with a couple other related issues).

from moq4.

After the recent merges, this might finally be fairly easy to fix.

from moq4.