This repository has been archived by the owner on Dec 19, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 226
Make TagHelperOutput
lazy initialize TagHelperContent
properties.
#358
Comments
Please see #317 for additional info. |
Please have a chat with @rynowak before starting the perf investigation. |
Yes. Let's discuss |
Hah! |
Upon investigating a proper fix for this issue I decided to investigate what it'd take to have This will also involve removing the |
NTaylorMullen
added a commit
that referenced
this issue
Nov 13, 2015
- This allows users to write `TagHelperOutput` directly to an `IHtmlContent` accepting `TextWriter`. - This also enables us to inspect backing fields for all of the various contents to lazily initialize them. #358
NTaylorMullen
added a commit
that referenced
this issue
Nov 13, 2015
- Added backing fields to each of the content properties and added null propagation checks throughout the class. #358
NTaylorMullen
added a commit
that referenced
this issue
Nov 13, 2015
- Added backing fields to each of the content properties and added null propagation checks throughout the class. #358
NTaylorMullen
added a commit
to aspnet/Mvc
that referenced
this issue
Nov 18, 2015
- Removed `WriteTagHelperAsync` methods from `RazorPage`. - Moved `WriteTagHelperAsync` tests into Razor since `TagHelperOutput` is now an `IHtmlContent`. - Updated code generation test files. aspnet/Razor#358
NTaylorMullen
added a commit
that referenced
this issue
Nov 18, 2015
- This allows users to write `TagHelperOutput` directly to an `IHtmlContent` accepting `TextWriter`. - This also enables us to inspect backing fields for all of the various contents to lazily initialize them. #358
NTaylorMullen
added a commit
that referenced
this issue
Nov 18, 2015
- Added backing fields to each of the content properties and added null propagation checks throughout the class. #358
NTaylorMullen
added a commit
that referenced
this issue
Nov 18, 2015
- Add `TagHelperOutput` unit tests. #358
NTaylorMullen
added a commit
that referenced
this issue
Nov 18, 2015
- This allows users to write `TagHelperOutput` directly to an `IHtmlContent` accepting `TextWriter`. - This also enables us to inspect backing fields for all of the various contents to lazily initialize them. #358
NTaylorMullen
added a commit
that referenced
this issue
Nov 18, 2015
- Added backing fields to each of the content properties and added null propagation checks throughout the class. #358
NTaylorMullen
added a commit
that referenced
this issue
Nov 18, 2015
- Add `TagHelperOutput` unit tests. #358
NTaylorMullen
added a commit
to aspnet/Mvc
that referenced
this issue
Nov 19, 2015
- Removed `WriteTagHelperAsync` methods from `RazorPage`. - Moved `WriteTagHelperAsync` tests into Razor since `TagHelperOutput` is now an `IHtmlContent`. - Updated code generation test files. aspnet/Razor#358
NTaylorMullen
added a commit
that referenced
this issue
Nov 20, 2015
- This allows users to write `TagHelperOutput` directly to an `IHtmlContent` accepting `TextWriter`. - This also enables us to inspect backing fields for all of the various contents to lazily initialize them. #358
NTaylorMullen
added a commit
that referenced
this issue
Nov 20, 2015
- Added backing fields to each of the content properties and added null propagation checks throughout the class. #358
NTaylorMullen
added a commit
that referenced
this issue
Nov 20, 2015
- Add `TagHelperOutput` unit tests. #358
NTaylorMullen
added a commit
that referenced
this issue
Nov 20, 2015
- This allows users to write `TagHelperOutput` directly to an `IHtmlContent` accepting `TextWriter`. - This also enables us to inspect backing fields for all of the various contents to lazily initialize them. #358
NTaylorMullen
added a commit
that referenced
this issue
Nov 20, 2015
- Added backing fields to each of the content properties and added null propagation checks throughout the class. #358
NTaylorMullen
added a commit
that referenced
this issue
Nov 20, 2015
- Add `TagHelperOutput` unit tests. #358
NTaylorMullen
added a commit
to aspnet/Mvc
that referenced
this issue
Nov 20, 2015
- Removed `WriteTagHelperAsync` methods from `RazorPage`. - Moved `WriteTagHelperAsync` tests into Razor since `TagHelperOutput` is now an `IHtmlContent`. - Updated code generation test files. aspnet/Razor#358
NTaylorMullen
added a commit
to aspnet/Mvc
that referenced
this issue
Nov 20, 2015
- Removed `WriteTagHelperAsync` methods from `RazorPage`. - Moved `WriteTagHelperAsync` tests into Razor since `TagHelperOutput` is now an `IHtmlContent`. - Updated code generation test files. aspnet/Razor#358
NTaylorMullen
changed the title
Analyze performance impact of TagHelperContent not being lazy on TagHelperOutput properties.
Make Nov 20, 2015
TagHelperOutput
lazy initialize TagHelperContent
properties.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The initial implementations of the "new"
TagHelperOutput
data structure (one with buffers instead of strings) was originally lazy with the buffers construction but was then removed due to the added complexity via code review. We should analyze its perf impact to determine if being lazy about construction ofPreElement
,PreContent
,Content
,PostContent
andPostElement
'sTagHelperContent
objects is beneficiary.The text was updated successfully, but these errors were encountered: