You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 9, 2024. It is now read-only.
When specifying a store sorter, its direction value is all caps in Razor markup, but is emitted lowercase. This causes Ext JS to obey the direction BUT does not show the sort arrow at all.
When sorting in ascending order, another bug with Ext.NET 7 makes it work, because when a value is specified -and- it matches whatever default Ext.NET thinks Ext JS has, Ext.NET does not emit the value at all. It means the direction: "asc" line is not output at all, and Ext JS uses default sorter direction.
In order to circumvent the issue, just define direction as a custom config:
When specifying a store sorter, its
direction
value is all caps in Razor markup, but is emitted lowercase. This causes Ext JS to obey the direction BUT does not show the sort arrow at all.According to Sencha documentation, the valid input to
direction
is either theASC
orDESC
strings.So this:
gets output as this:
Which results in the above error.
When sorting in ascending order, another bug with Ext.NET 7 makes it work, because when a value is specified -and- it matches whatever default Ext.NET thinks Ext JS has, Ext.NET does not emit the value at all. It means the
direction: "asc"
line is not output at all, and Ext JS uses default sorter direction.In order to circumvent the issue, just define direction as a custom config:
The text was updated successfully, but these errors were encountered: