Completed
Last Updated: 13 Oct 2020 18:48 by ADMIN
Release 2020.R3.SP.next
Created by: Bryan Patrick
Comments: 5
Category: Filter
Type: Bug Report
2

Bug report

Filter component operators are always rendered in the initial order, regardless of the specified order

Reproduction of the problem

This code:

.Fields(f =>
      {
          f.Add(p=>p.FirstName).Operators(o =>
                o.String(n =>n
                    .Contains("Contains")
                    .Eq("Is equal to")
                    .Custom("john", c => c.Text("John").Handler("oddNumbersHandler"))
                    )
                );

Renders to this:

Expected/desired behavior
The order of the operators shall be in the predefined order.

Environment
Kendo UI version: [all]
Browser: [all]

Unplanned
Last Updated: 02 Oct 2020 08:21 by ADMIN
Created by: Bryan Patrick
Comments: 0
Category: Filter
Type: Feature Request
0

Feature Enhancement
Expose Default Operator for Filter fields

Current behavior
Apart from setting FilterExpression to render filed with a certain operator, there is no option for setting a Default Operator for the fields

.FilterExpression(f =>
      {
          f.Add(p => p.FirstName).Contains("Jeremy");
      })

The above renders the Contains operator initially but if you change the field and return back to the FirstName field the operator is no longer Contains.

Expected/desired behavior
Default Operator for FIlter fields shall be exposed

Environment
Kendo UI version: all
Browser: al