nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

As stated in the docs, "Currently, ListMapper supports one
transformation: creating a collection of property values. "

It's certainly possible to add a feature that accesses fields in 3.0
although it's possible that the whole thing will be replaced with the
use of lambdas.

We'll use this bug as a placeholder for the issue, however it turns out.

** Changed in: nunit-3.0
       Status: New => Triaged

** Changed in: nunit-3.0
   Importance: Undecided => Wishlist

-- 
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