sort_by has unexpected behavior when certain fields are not represented as float

I have some content with a Number field price_start.
Some inputs are represented with a trailing decimal unit (xxx.0) and some don’t (xxx)

When sorting with content.price_start:asc:float, it fails to sort the expected way IF all fields are not represented with a trailing decimal unit (xxx.0). This is rather odd behavior as even if you don’t explicitly represent data as a float the conversion of an integer to float is kind of expected when handling numeric data.

Hello @DEV-ONI,

I passed your report for analysis to our developers and will keep you updated about the state.

Best regards

1 Like