Support custom properties in SearchContext.CurrentSearchResults
When developing a custom index you currently are limited in what you can store in the index. Only the default search fields are supported, but you cannot add your own custom columns to the DataRow object in SearchContext.CurrentSearchResults.
Adding custom columns to the DataRow would be a welcome feature that is in line with way Kentico wants to approach MVC. Sometimes a simple 'Pages' index is just not enough to display data and you want to avoid doing database queries to gather more information about the search results.
Currently for custom indexes, the DataRow is being created hardcoded (see attached file) and it would be ideal to move this logic away to the Custom Index code, to have full control of what is stored in the index and is returned in the DataRow.
Of course, there is a workaround to this (storing XML in a field that can be stored for example), but this is far from ideal.