On 6/2/14 10:46 AM, "Michael A. Labriola" <labri...@digitalprimates.net> wrote:
>>A totally reasonable scenario. It is tempting to simply remove this >>check, but you never know when someone is relying on this behavior. > >I am not really suggesting that we remove it completely, just rather that >we consider it an OR. A SortField's name must either be valid or it must >have a compareFunction. Makes sense and we probably should have done that in the first place. But since we didn't, do we change behavior and risk breaking folks or add a flag and keep both code paths? -Alex
