`undefined` cannot be removed from `sortDirections`

• I have searched the issues of this repository and believe that this is not a duplicate.

Reproduction link

Steps to reproduce

Set sortDirections to any set that does not include undefined. Sorting will still cycle between the defined directions and undefined.

What is expected?

If sortDirections is ["ascend","descend"] or ["ascend"] then only the specified directions should be allowed.

What is actually happening?

Clicking the column header multiple times will change direction and will always include the undefined sort order.

Environment	Info
antd	3.15.0
React	16.8.4
System	Mac?
Browser	Chrome

---

My table loads remote data which will always be sorted by one column. If a user sorts by a column, they must change direction or sort by another column. It does not make sense here to specify a column with an order of undefined.

[StallionV]

It’s not a bug. Column should aways enable user to set sort state back after sortDirections end. If you want to lock the sortOrder without default. You can use controlled sortOrder instead: https://codesandbox.io/s/jz071jrm7y

Well that way you are forcing users to write custom sortOrders. I agree with @roblingle where by default we should be able to specify what states to allow for sorting. [ascend, descend, default] or only [ascend, descend]. Also the documentation is confusing because looking at the description for sortDirections it kind of leads a user to think that you can specify the type of sorts allowed

[zombieJ]

It’s not a bug. Column should aways enable user to set sort state back after sortDirections end. If you want to lock the sortOrder without default. You can use controlled sortOrder instead: https://codesandbox.io/s/jz071jrm7y