nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

We have other places in the NUnit syntax where we accept equally
Properties, Fields and Methods. We just don't use the word 'Property' to
describe them. Perhaps that's the way to handle this. Once we are using
the word 'Property' we are conceptually at a level of implementation,
below the point where fields and properties are interchangeable.

In fact, I think it would be desireable to get rid of the need to
specify strings as names entirely, which is why I lean more toward the
use of Lambdas in the future.

-- 
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
https://bugs.launchpad.net/bugs/996427

Title:
  ListMapper.Property doesn't work with fields

Status in NUnit Test Framework:
  Triaged

Bug description:
  When using the ListMapper to perform a task such as: 
  > List.Map(values).Property("subValue") 
  the expected outcome (a list of subValues) is achieved if the property subValue is encapsulated (get/set), but not if it's a field.

  I'd assume this is a reflection quirk, but I'm not up on the details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunit-3.0/+bug/996427/+subscriptions