[Solved] Why is MaxAllowedTags implemented so poorly and the docs are misleading?

[Rami]

With version, I believe, 14.1.0, you added the MaxAllowedTags property to the MultiSelect. The docs claim that "To restrict the allowed number of individual tags, use the MaxAllowedTags parameter". This of course implies that if I don't set the MaxAllowedTags property, the number of tags is not restricted and the old behaviour is retained. Which is how it should've been!

But now, if I want to update to a newer release, I seemingly have to go to EVERY SINGLE MultiSelect in all of my apps and add a very irritating "MaxAllowedTags=999" or something on them. This can be observed and played with in a Repl for anyone interested.

So my question is, why did you make it so the established default behaviour of the component was not preserved, but instead broken with the addition of MaxAllowedTags? And yes, I do have multiselects with over 10 tags that I need to display all at once.

As a bonus irritation, the MultiSelect overview page doesn't even mention either MaxAllowedTags or TagMode parameters!

[Dimo]

Hi Rami,

Indeed, when we introduced the MultiSelect "Select All" functionality, we also conducted a UX review of the component and decided that a default MaxAllowedTags of 10 serves the majority of users and the most common scenarios. I am sorry if this isn't true for your case and you need to adjust the component settings. There are two ways to do that in a scalable manner, so that you set MaxAllowedTags in a single place - Blazor component inheritance or composition.

I also added MaxAllowedTags to the parameter table on the MultiSelect Overview page and the changes will go live shortly. Thanks for pointing this out - I updated your Telerik points.

Regards,
Dimo
Progress Telerik

[Craig]

redacted

[Rami]

No, inheriting or compositing the MultiSelect into a new component is an even worse solution. Then I'd have to have some MyMultiSelect lugged around everywhere just to have it set MaxAllowedTags=999, but with the added cost of having every parameter "pass through". I guess I really just have to go to every instance and add MaxAllowedTags=999. I can't state how much I wish you would've made it so not having MaxAllowedTags set would've continued with the old behaviour and then if you want to set it, you can.

[Dimo]

Setting the parameter explicitly in the existing MultiSelect instances is certainly a valid approach. However, perhaps MaxAllowedTags="@null" better reflects your needs and matches the old default configuration.

[Rami]

Ok, thanks, @null there is a little better than an arbitrary number. Once again, this behaviour isn't documented anywhere that I see. Also the TagMode parameter is still left out?

[Dimo]

Hi Rami, the MaxAllowedTags change was documented yesterday at Breaking Changes in version 15.0.0 and I will also add TagMode to the parameter table shortly. Generally, we are gradually phasing out these tables as duplicate information, so I recommend to consult the MultiSelect API reference directly.