For example in DropDownList reflection is used for binding for TextField and ValueField.
As an additional option, I'd instead to be able to do DropDownList<FooBarModel> and then FooBarModel implements a Telerik interface IDropDownListItem (for example but use your naming conventions)
I agree you shouldn't remove the option of using TextField / ValueField but I'd like to see it as an option.
Doing the same thing in something like DataGrid I agree would be a ton more work and we'd likely require using source generation.
It seems that Microsoft / the industry is consistently recommending to phase out the use of reflection and have invested a bunch in making source generation much less of a pain and developer friendly.
I like how Robert suggested to do it in the linked article better then I explained, although he has different reasons for wanting it. Looking at Microsoft library https://www.fluentui-blazor.net/Select This is how they have implemented and it looks like they have done a lot of work at making their library aot friendly. The reasons stated by Telerik in the 2021 feedback article to not support Func<T, string> bindings appear to be either incorrect or are now incorrect. I strongly suggest to reconsider your stance.
The industry as a whole is moving away from using Reflection. It's important in order to take best advantage of AOT compiling
I would like to see:
Hi Nicholas,
If I understand correctly, you would like to bind the DropDownList Value parameter to a complex object rather than something like int or string. Is this correct?
If yes, then we have already declined such requests in the past. If you are thinking about something different, please elaborate.
Regards,
Dimo
Progress Telerik
Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.