PHPackages ptplugins/filament-number-input - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Localization & i18n](/categories/localization) 4. / 5. ptplugins/filament-number-input ActiveLibrary[Localization & i18n](/categories/localization) ptplugins/filament-number-input =============================== Locale-aware numeric input field for FilamentPHP. Formats decimal and thousands separators in the browser while always storing a clean float for the database. 1.0.0(today)00MITBladePHP ^8.1 Since Jun 13Pushed todayCompare [ Source](https://github.com/ptplugins/filament-number-input)[ Packagist](https://packagist.org/packages/ptplugins/filament-number-input)[ Docs](https://ptplugins.com/filament-number-input)[ RSS](/packages/ptplugins-filament-number-input/feed)WikiDiscussions main Synced today READMEChangelog (3)Dependencies (2)Versions (2)Used By (0) Filament Number Input ===================== [](#filament-number-input) [![Filament Number Input β€” locale-aware numeric field that stores a clean float](./screenshot.png)](./screenshot.png) > A locale-aware numeric input field for [FilamentPHP](https://filamentphp.com/) **v3, v4, and v5**. The user types and sees a localized number (European `12.345,67` or US `12,345.67`); your model always stores a clean float (`12345.67`). Single codebase across all three Filament major versions β€” same field, same API. [![Buy us a beer](https://camo.githubusercontent.com/1bef23d3b523a63534746f730a172d71f7bc0f925da66b491b6997a778c7777c/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f2546302539462538442542412d427579253230757325323061253230626565722d79656c6c6f77)](https://ptplugins.com/buy-us-a-beer) **🎯 [Try it live Β· ptplugins.com/demo/number-input](https://ptplugins.com/demo/number-input)** β€” type a number and watch the stored float update. The problem ----------- [](#the-problem) Localized number formatting is one of those things that looks trivial and then quietly corrupts your data for a year. If you let a localized string reach the database β€” `"12.345,67"` β€” everything downstream breaks: - `SUM()` / `AVG()` and any SQL math return garbage or zero. - `decimal` / `float` casts silently truncate at the first separator (`"12.345,67"` β†’ `12.345` or `12`). - Sorting is lexical, not numeric. - The moment two users have different locales (`12.345,67` vs `12,345.67`), the same column holds two incompatible formats. And the naive fix β€” "just format on the front end" β€” has its own trap: any value set **programmatically** (a seeder, an import, `$set('amount', '12,34')`, a copy/paste) never passes through the browser formatter, so the localized string slips straight into the model. This field solves both ends. **The database only ever sees a plain float**, no matter how the value was entered β€” exactly the same contract as a well-behaved date picker that stores ISO `Y-m-d` while showing `d.m.Y`. How it works β€” two cooperating layers ------------------------------------- [](#how-it-works--two-cooperating-layers) ``` β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ browser ───────────────────────────┐ user β†’ β”‚ formattedValue (x-model, LOCAL Alpine state) "12.345,67" β”‚ types β”‚ β”‚ parseNumber() β”‚ β”‚ β–Ό β”‚ β”‚ rawValue ($wire.entangle, the ONLY thing synced) 12345.67 β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”‚β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β–Ό β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ server ──────────────────────────┐ β”‚ normalizeToFloat() β€” idempotent safety net β”‚ β†’ DB: 12345.67 (float) β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ ``` 1. **Primary layer (JavaScript).** An Alpine component formats and parses as the user types. The localized text lives only in `formattedValue`, which is bound to the input via `x-model` and **never leaves the browser**. The only value entangled with the server is `rawValue` β€” already a parsed float. In the normal interactive flow, the server never even sees a localized string. 2. **Safety net (PHP).** `dehydrateStateUsing()` runs `normalizeToFloat()`, and a validation rule guards bad input. This layer exists for values that **bypass** the browser entirely β€” programmatic `$set()`, imports, seeders, paste into a non-rendered field. It is **idempotent for anything already numeric**: an int/float (or canonical numeric string) is returned unchanged, so it can never corrupt the clean float the JS layer produced. It only does work on a localized *string*. Both layers read the **same** separator configuration, so they can never disagree. > Why two layers and not just one? JS alone leaks on programmatic writes; PHP alone means re-implementing locale parsing on the server and giving up live, in-field formatting. Together: live UX **and** a hard guarantee at the storage boundary. Installation ------------ [](#installation) ``` composer require ptplugins/filament-number-input ``` The package auto-discovers its service provider. There are no assets to publish β€” the Alpine logic ships inline with the field's Blade view. Quick start ----------- [](#quick-start) ``` use PtPlugins\FilamentNumberInput\Fields\NumberInput; NumberInput::make('price'); ``` That's it. The default is the European convention (dot groups thousands, comma marks decimals). The bound model attribute will be a float. Configuration ------------- [](#configuration) ### Presets [](#presets) ``` NumberInput::make('price')->european(); // 12.345,67 (default) NumberInput::make('price')->american(); // 12,345.67 ``` ### Custom separators [](#custom-separators) ``` NumberInput::make('price') ->decimalSeparator(',') ->thousandsSeparator(' ') // e.g. "12 345,67" (French / SI style) ->decimalPlaces(2); ``` MethodDefaultDescription`decimalSeparator(string|Closure)``,`Character shown between integer and decimal part`thousandsSeparator(string|Closure)``.`Character grouping thousands`decimalPlaces(int|Closure)``2`Zero-padding added on blur when the user typed no decimals (`12` β†’ `12,00`)`european()`β€”Shortcut for `,` decimal / `.` thousands`american()`β€”Shortcut for `.` decimal / `,` thousandsAll four accept a closure, so separators can depend on the record or the authenticated user's locale. `NumberInput` **extends Filament's `TextInput`**, so every `TextInput` method works unchanged β€” `->required()`, `->prefix('€')`, `->suffix('RSD')`, `->disabled()`, `->placeholder()`, affix icons and actions, `->live()`, and so on. Storage guarantee ----------------- [](#storage-guarantee) Whatever the display format, the dehydrated state is a PHP `float`: ``` NumberInput::make('price')->european(); // user sees 1.234,56 β†’ model stores 1234.56 NumberInput::make('price')->american(); // user sees 1,234.56 β†’ model stores 1234.56 // And directly, for imports/seeders, the same parsing is available: NumberInput::make('price')->european()->normalizeToFloat('1.234,56'); // 1234.56 NumberInput::make('price')->american()->normalizeToFloat('1,234.56'); // 1234.56 NumberInput::make('price')->normalizeToFloat(1234.56); // 1234.56 (unchanged) NumberInput::make('price')->normalizeToFloat(''); // null ``` Unparseable input is returned untouched so the validation rule rejects it, rather than silently corrupting the stored value. Edge cases & gotchas (learned the hard way) ----------------------------------------------- [](#edge-cases--gotchas-learned-the-hard-way) These are the real-world traps we hit running an earlier version of this field across a production Filament app. They're documented here so you don't have to rediscover them. - **Programmatic `$set()` with a localized string.** `$set('amount', '12,34')` never runs the JS parser. Without the PHP safety net, that string lands in the database verbatim. With it, it's normalized on dehydrate. This is *the* reason the PHP layer exists. - **The lone-dot ambiguity in European mode.** In EU mode a value like `"1.234"` (no decimal comma) is ambiguous: is it *one thousand two hundred thirty-four* (dot = thousands) or *1.234* (a native float)? Both the JS and PHP layers resolve it the **same** way β€” as a native float `1.234` β€” so a programmatically-set float survives the round trip intact. If you mean 1234, set the integer `1234`, not the string `"1.234"`. - **Don't reach for `->mask()`.** An obvious-looking approach is a Filament money mask (`RawJs::make('$money(...)')`) plus a PHP `dehydrateStateUsing`. We shipped that first. It's brittle: the mask, the dehydrator and a `formatStateUsing` hook all have to agree, edits mid-string fight the mask cursor, and pasted/programmatic values slip past. This field replaces that whole dance with one Alpine component that owns formatting end to end. Just use `NumberInput`; don't add a mask on top. - **`decimalPlaces` only pads on blur.** Typing `12` and tabbing away shows `12,00`. It does not force precision while typing, and it does not round β€” it's a display convenience, not a rounding policy. Round in your cast/mutator if you need fixed precision in storage. - **Decimals shown β‰  precision stored.** The field stores the full parsed float. If you want the database value clamped to N decimals, do it in the model (`decimal:2` cast), not here. Filament v3 / v4 / v5 --------------------- [](#filament-v3--v4--v5) One codebase serves all three. The field extends `TextInput` (stable across versions) and the Blade view uses only the cross-version `` / `` primitives β€” not the internal markup that Filament reshuffled between v3 and v4. State binding goes through `applyStateBindingModifiers`, so `->live()` / deferred behaviour follows whatever the host version does. Verified against Filament v4.7.2 (`view:cache` compile) in addition to v3. Requirements ------------ [](#requirements) - PHP 8.1+ - Filament 3.x, 4.x, or 5.x License ------- [](#license) MIT β€” see [LICENSE.md](LICENSE.md). --- Part of the [ptplugins.com](https://ptplugins.com) collection of FilamentPHP plugins. ### Health Score 38 β€” LowBetter than 83% of packages Maintenance100 Actively maintained with recent releases Popularity0 Limited adoption so far Community2 Small or concentrated contributor base Maturity42 Maturing project, gaining track record How is this calculated?**Maintenance (25%)** β€” Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** β€” Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** β€” Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** β€” Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Unknown Total 1 Last Release 0d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/58f7e578abcf85b80036e2d54969fe0926997218a40aff6b517dd26fa38fdba9?d=identicon)[Premke](/maintainers/Premke) --- Tags laravelcurrencylocaleformattinginputnumberfilamentfilamentphpform-field ### Embed Badge ![Health badge](/badges/ptplugins-filament-number-input/health.svg) ``` [![Health](https://phpackages.com/badges/ptplugins-filament-number-input/health.svg)](https://phpackages.com/packages/ptplugins-filament-number-input) ``` ### Alternatives [rawilk/profile-filament-plugin Profile & MFA starter kit for filament. 3913.7k](/packages/rawilk-profile-filament-plugin)[bezhansalleh/filament-language-switch Zero config Language Switch(Changer/Localizer) plugin for filamentphp admin 3571.2M21](/packages/bezhansalleh-filament-language-switch)[marcelweidum/filament-passkeys Use passkeys in your filamentphp app 6643.3k](/packages/marcelweidum-filament-passkeys)[dotswan/filament-map-picker Easily pick and retrieve geo-coordinates using a map-based interface in your Filament applications. 128173.7k3](/packages/dotswan-filament-map-picker)[stephenjude/filament-jetstream A Laravel starter kit built with Filament inspired by Jetstream. 17758.9k2](/packages/stephenjude-filament-jetstream)[stephenjude/filament-two-factor-authentication Filament Two Factor Authentication: Google 2FA + Passkey Authentication 84192.9k7](/packages/stephenjude-filament-two-factor-authentication) PHPackages Β© 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)