Description

This is an early prototype for an idea that can be found here: #6049 (comment). Essentially, it allows to wire up any type to the filter. For example, if there is a lack of support for TimeOnly, one can implement their own FilterTypeBase and add the corresponding UI part to handle it.

Initially, I had a simple idea:

public interface ITypeFilter
{
	bool CanBeMapped { get; }
	RenderFragment RenderFilterFragment<T>(FilterDefinition<T> filterDefinition, Filter<T> filter);
}

However, I encountered the issue of an external render fragment interfering with the render lifecycle and throwing an error: System.InvalidOperationException: 'The render handle is not yet assigned.'

I attempted three prototypes before settling on the current implementation, which uses DynamicComponent and ensures that the render lifecycle works correctly. My previous prototypes required "hacks" that probably wouldn't be accepted, which is why I decided to go with the current solution.

How Has This Been Tested?

Unit test + new unit tests(incoming)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• The PR is submitted to the correct branch (dev).
• My code follows the code style of this project.
• I've added relevant tests.