-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Adding IView.Path and ViewContext.ExecutingPagePath #1996
Conversation
cc @DamianEdwards \ @dougbu |
/// Asynchronously renders the view using the specified <paramref name="content"/>. | ||
/// </summary> | ||
/// <param name="context">The <see cref="ViewContext"/>.</param> | ||
/// <returns>A <see cref="Task"/> rthat represents the asynchronous rendering.</returns> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- typo: "that"
- avoid "represents" since it's meaningless. suggest
A <see cref="Task"/> that on completion renders the view.
⌚ |
when @dougbu is happy with the comments |
Updated. |
I'm reluctant about the lambda property for a read only value. if you can hold off pushing, let's talk about that tomorrow. |
public interface IView | ||
{ | ||
/// <summary> | ||
/// Gets the path of the view as resolved by the <see cref="ViewResult"/>. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doesn't this come from the view engine? there's nothing stopping you from using this outside of ViewResult
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Fixes #1940