float_without_trailing_zeros

Time off accrual plans in Odoo are configured as sentences: "employee accrues 1 day every month, capped at 15 days". The numbers in those sentences are float fields, and a float formatted to the usual two decimals reads "1.00 day every month", which is technically fine and visually wrong. This widget exists to make those inline numbers read like prose.

It extends the standard float widget and overrides exactly one thing, the formattedValue getter, chaining two replacements: first (\.\d*?[1-9])0+$ drops zeros that follow the last significant decimal digit, turning 2.50 into 2.5, then \.0+$ drops a decimal part that is entirely zeros, turning 1.00 into 1. Everything else, parsing, editing, digits handling, validation, is the inherited float widget.

Because only the formatted display is touched, the field edits like any float: click into it and the input shows the standard representation, save and the trimmed version returns.

This is a polish widget, and polish is the actual point. Configuration screens that read as sentences, accrual plans, pricing rules, thresholds, get skimmed by managers who approve them. "1.00 days" in the middle of a sentence is exactly the kind of trailing noise that makes a screen feel machine-written, and enough of it erodes confidence in what is being approved.

For customizers the practical question in 2026 is which tool to reach for. If you are building for Odoo 19 or later, the core float widget's hide_trailing_zeros option does the same visual job, works in list cells and during formatting generally, and needs no module dependency beyond web. This widget earns its keep when you must match core HR behavior exactly, when the view also targets 17 or 18 where the core option does not exist, or when you specifically want trimming only in readonly display while keeping full precision visible during edits.

One data note: the widget never rounds. A stored 1.25 with two display digits renders 1.25 either way; only zeros disappear. Nothing about accrual math changes.

As core uses it in accrual plans

<field nolabel="1" class="me-1 o_field_accrual" name="added_value"
       widget="float_without_trailing_zeros"/>

The number sits inline before a unit selector, forming the accrual sentence.

With explicit precision

<field name="threshold" widget="float_without_trailing_zeros"
       options="{'digits': [16, 3]}"/>

Digits control the formatting before trimming: 1.200 renders as 1.2, 1.230 as 1.23.

The Odoo 19 core alternative

<field name="threshold" widget="float"
       options="{'hide_trailing_zeros': True}"/>

Same visual result on 19+, no hr dependency, and it also applies in editable lists.

Three version-archaeology facts define this widget better than its fourteen lines.

The 16 version trimmed only in readonly, differently. It lived in hr_holidays as a legacy-framework field that reformatted the readonly text through parseFloat, which incidentally also dropped trailing zeros after the decimal in its own way. The move to hr and the modern getter came in 17.

17 and 18 had a blind spot. Their single regex \.0+$ removed only decimal parts that were entirely zeros. An accrual of 2.50 days displayed as "2.50", while 2.00 displayed as "2". The second regex closing that gap, so 2.50 reads "2.5", appears in 19.0, and it is the kind of tiny inconsistency users notice on approval screens without being able to name it.

19 made the widget almost obsolete. The same release gave core float the hide_trailing_zeros option, implemented properly at the formatter level (trailingZeros: false), which also covers list rendering. The hr widget survives because core HR views still use it and because its trimming applies regardless of options passed. When patching or extending accrual views, either mechanism is fine; when building new views on 19+, the core option is the cleaner dependency.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. These notes are read from the public development branch, which is unstable until feature freeze; we re-verify against the shipped release.

The file is byte-identical on master: same two regexes, same registration, no options added or removed. The inherited float widget on master continues to carry hide_trailing_zeros. Barring late changes, this page should hold for Odoo 20 as written, and the long-term question is simply whether Odoo eventually retires the hr widget in favor of the core option; nothing on the branch suggests it yet.