Support for unsigned integer types such as ulong, ushort, byte

Progress® Telerik® UI for Blazor Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 04 Jul 2022 14:04 by Hans

Release 3.4.0

Jan Heiko Houtrouw

Created on: 20 Nov 2019 07:32

Category: Grid

Type: Feature Request

Support for unsigned integer types such as ulong, ushort, byte

Hello Team,

I am using "FilterMode="GridFilterMode.FilterRow". For int values there is a "numeric chooser" in the column header and the filter option "contains" is not available.

This is the correct behaviour. But when I bind the column to a ulong, ushort, ... value theses seems to be considered as string. There is no "numeric chooser" and the filter "contains" is available, which resullts in further problems with the OData endpoint.

8 comments

Hans

Posted on: 04 Jul 2022 14:04

Oh never mind, I joust found out it's fixed in v3.4.0 - thx

Hans

Posted on: 04 Jul 2022 13:50

Yes, please implement this.

we rewuire this for editing Unsigned integer ID's

ADMIN

Stamo Gochev

Posted on: 24 Sep 2021 07:34

Hi all,

I've added the suggestion for throwing an exception instead of making a fallback to a string editor so that this idea can be reconsidered. This will provide better information about what is happening when an unsupported type is used.

Regards,
Stamo Gochev
Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.

Chris

Posted on: 17 Sep 2021 17:08

We need this for editing byte fields and the view model workaround is pretty messy. In the meantime, maybe have the grid component throw a warning/error about unsupported types? Right now it looks like it's going to work and then fails silently which means we're all wasting a lot of time trying to figure out what's wrong.

ADMIN

Marin Bratanov

Posted on: 02 Jul 2020 07:59

A status update on this task - this is considered an enhancement and so I renamed it accordingly. At the moment, unsigned integers are not implemented in the numeric textbox and the grid.

A workaround for them (full list here) could be using a view-model that uses signed integers that can accommodate those values.

Regards,
Marin Bratanov
Progress Telerik

Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.

ADMIN

Marin Bratanov

Posted on: 28 Apr 2020 15:57

Hello Jan,

At this point, you are the only person who has hit this issue and thus its priority is not very high. I have bumped it for you just now, to go as high as it can, though. What I can say at this point is that the issue is not very trivial, because it requires implementation in the numeric textbox with is the editor that will be used for such numbers, so it is not just adding a few types to a list (even then, there is a lot more code than just adding type names to it).

Regards,
Marin Bratanov
Progress Telerik

Jan Heiko Houtrouw

Posted on: 28 Apr 2020 12:01

Hello Team,

This bug is very annyoing for us. When is a fix available ? From my understanding the solution is simple. The type must be just added to the list for numerics.

Thanks !

ADMIN

Marin Bratanov

Posted on: 20 Nov 2019 10:41

Hi Jan,

I moved this to the feedback portal so you can Follow it. Here's a link for you: https://feedback.telerik.com/blazor/1443000-numeric-values-ulong-ushort-are-detected-as-string-in-the-filter-row.

These particular types (ulong and ushort) are not recognized as numbers simply because we haven't added them to the list, and that's why they fall back to the filter options for strings.

Regards,
Marin Bratanov
Progress Telerik

UI for Blazor