Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Update Expression-Translation-(UseAsDataSource).md
fix typos
  • Loading branch information
jjjmuniz authored Feb 12, 2020
commit 9f57b22e138ec9b9e1a9d09a2448680dadeee7c2
4 changes: 2 additions & 2 deletions docs/Expression-Translation-(UseAsDataSource).md
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,7 @@ Does the equivalent of

### When ProjectTo() is not called

Expression Translation works for all kinds of functions, including `Select` calls. If `Select` is used after `UseAsDataSource()` and changes return type, then `ProjectTo<>()` won't be called and value with be returned instead using `mapper.Map`.
Expression Translation works for all kinds of functions, including `Select` calls. If `Select` is used after `UseAsDataSource()` and changes return type, then `ProjectTo<>()` won't be called and value will be returned instead using `mapper.Map`.

Example:

Expand Down Expand Up @@ -154,7 +154,7 @@ public List<OrderLineDTO> GetLinesForOrder(int orderId)
}
```

However, if you did this with the `.UseAsDataSource()` approach, you would loose all its power - namely its ability to modify the internal expression until it is enumerated.
However, if you did this with the `.UseAsDataSource()` approach, you would lose all of its power - namely its ability to modify the internal expression until it is enumerated.
To solve that problem, we introduced the `.OnEnumerated` callback.
Using it, you can do the following:

Expand Down