aspnetcore/test/WebSites/HtmlGenerationWebSite/Controllers
Doug Bunting 27283ec098 Make `string`-based expression evaluations behave consistently
- #1485, #1487
 - handle `TemplateInfo.HtmlFieldPrefix` in `ViewDataEvaluator.Eval()`
  - attempt lookup in the `ViewDataDictionary` using full name then evaluate
    relative `expression` against `viewData.Model`
  - handle `null` or empty `expression` special case in this method (remove `throw`s)
 - always pass relative `expression` name into `Eval()`
  - remove `null` or empty `expression` handling from higher-level code
  - in a couple of cases, special-case returned `ViewDataInfo`
- #2662
 - remove incorrect guard from `DefaultHtmlGenerator.GenerateRadioButtion()`
- add doc comments for the core methods that have changed
- enable unit tests skipped due to one of above bugs
 - fix one (yeah, just one) other test with incorrect expectations
- remove functional test comments about the above bugs and update expectations

nits:
- move some comments describing `ViewDataEvaluator` methods above the methods
2015-06-16 21:54:56 -07:00
..
Catalog_CacheTagHelperController.cs Rename `MvcTagHelpersWebSite` to `HtmlGenerationsWebSite` 2015-06-05 20:30:17 -07:00
HtmlGeneration_HomeController.cs Make `string`-based expression evaluations behave consistently 2015-06-16 21:54:56 -07:00
HtmlGeneration_OrderController.cs Rename `MvcTagHelpersWebSite` to `HtmlGenerationsWebSite` 2015-06-05 20:30:17 -07:00
HtmlGeneration_ProductController.cs Rename `MvcTagHelpersWebSite` to `HtmlGenerationsWebSite` 2015-06-05 20:30:17 -07:00