If you have a class decorated with Queryable and then override the OData Queryable on a specific method in that class with ODataQueryOptions the Queryable Attribute will still throw a not supported error even if you have implemented that specific $filter.
This is a pretty common case where you'd want the default Queryable and then customize one or two methods in the class. Taking the Queryable attribute off the class and putting it on each method is highly non-optimal because of the maintenance issue that would be created.
The QueryableAttribute should recognize the docoration on the call and not throw if the method has a parameter of type ODataQueryOptions.
Comments: How does one tell the EnableQuerySupport function to use my version of the Queryable attribute instead of the default one? I still need to back fill $select until you guys finally get around to it.
This is a pretty common case where you'd want the default Queryable and then customize one or two methods in the class. Taking the Queryable attribute off the class and putting it on each method is highly non-optimal because of the maintenance issue that would be created.
The QueryableAttribute should recognize the docoration on the call and not throw if the method has a parameter of type ODataQueryOptions.
Comments: How does one tell the EnableQuerySupport function to use my version of the Queryable attribute instead of the default one? I still need to back fill $select until you guys finally get around to it.