Add ViewData
for internal view owned state
#176
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This add
ViewData
for internal view owned state.Storing view state in
ViewData
instead ofViewState
has a couple of benefits:The downside is that updating
ViewData
by a message requires walking the view tree, which is probably more expensive.Overall I think it's a good tradeoff as it favors view passes and view creation which does seem to be the slowest parts.
The
style
field is moved fromViewState
toViewData
.