A scale-2 money field over a four-decimal column (the documented fee example) was served "12.5000" and answered money.too_precise when the untouched value was saved back. Trailing zeros carry no precision, so the server check and the SPA parser count only significant fraction digits; the value still reaches the column unchanged, never rounded or truncated. - cabana validateMoneyValue and admin parseMoneyInput trim trailing zeros before the scale comparison - forms docs and cabana README name the rule; embedded dist rebuilt - MoneyField spec asserts 12.5000 at scale 2 is accepted, 12.5010 refused
17 lines
579 B
HTML
17 lines
579 B
HTML
<!doctype html>
|
|
<html lang="pl">
|
|
<head>
|
|
<meta charset="UTF-8" />
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
|
|
<meta name="robots" content="noindex, nofollow" />
|
|
<meta name="summer-admin-base" content="__SUMMER_ADMIN_BASE__" />
|
|
<link rel="icon" href="./favicon.ico" sizes="48x48" />
|
|
<title>SummerCMS</title>
|
|
<script type="module" crossorigin src="./assets/index-DYW0Mjwc.js"></script>
|
|
<link rel="stylesheet" crossorigin href="./assets/index-c6AgbZf1.css">
|
|
</head>
|
|
<body>
|
|
<div id="app"></div>
|
|
</body>
|
|
</html>
|