DataFilter resets FilterOperator to default after setting Filters property

I am trying to implement saving and loading filter settings for DataFilter by reading, saving, then setting again the Filters property. Filter settings are saved and restored well, but not the FilterOperator. Code to reproduce (works also in your demo)

@using RadzenBlazorDemos.Data
@using RadzenBlazorDemos.Models.Northwind
@using Microsoft.EntityFrameworkCore
@using System.Linq.Dynamic.Core
@inherits DbContextPage

<RadzenButton Text="Save Filter" Click="@SaveFilter" />
<RadzenButton Text="Load Filter" Click="@LoadFilter" />

<RadzenDataFilter @ref="dataFilter" TItem="Order">
	<Properties>
		<RadzenDataFilterProperty TItem="Order" Property="OrderID" Title="Order ID" />
	</Properties>
</RadzenDataFilter>

@code {
	RadzenDataFilter<Order> dataFilter;	
	IEnumerable<CompositeFilterDescriptor> filters;	    

	void SaveFilter() => filters = dataFilter.Filters;

    void LoadFilter()
    {
		dataFilter.Filters = filters;
        StateHasChanged();
    }
}

Just add a pair of filters (they are added with default filter operator, according to filter value type, as far as I understood):

Make some settings, so filters are no more default. Press "Save Filter".

Remove filters by clicking on the cross sign right to the "Add/Or" buttons of the filter. Then press "Load Filter" - filter values are restored, but not filter operators (they get their default values):

Checked only for FilterOperator and FilterValue properties. Maybe other props are also reset to their defaults.

Perhaps I can restore filters properly with DataFilter methods like ClearFilters, then AddFilter - didn't try yet... but shoudn't just setting Filters property work also?

We're also running into this issue - and we're unable to get a workaround going via AddFilter().

It seems like Radzen team fixed this bug.

Tried my code from above in their demo - it works now as it should be. Tried it in my project - now it requires some changes, because CompositeFilterDescriptor.FilterOperator is nullable now. But anyway it is good.