merge(['class' => 'form-group'. $errors_class]) }}> @if (isset($label)) {{ $label }} @endif @php $blade_type = in_array($type, ['text', 'email', 'url', 'tel', 'number', 'password']) ? 'text' : $type; // Maxlength precedence: // 1. Explicit :maxlength="..." from the caller (always wins). // 2. Model rules — Helper::fieldMaxLength reads `max:N` from the // model's validation rules so the browser cap matches the DB // column width automatically. Applied to all types except // textarea/number (textareas back TEXT columns with no length // limit; browsers ignore maxlength on type="number"). // 3. Fallback 191 for text-family types (matches the vast majority // of varchar(191) columns in this schema). $effective_maxlength = $maxlength ?? ($type !== 'textarea' && $type !== 'number' ? Helper::fieldMaxLength($item, $name) : null) ?? (in_array($type, ['text', 'email', 'url', 'tel', 'password']) ? 191 : null); @endphp

{{-- You can pass an ... when the field needs custom markup (e.g. an input plus a select side by side, or a widget the input.* components don't cover). The wrapping label + error + help + aria still come from , so only the input area is hand-authored. --}} @isset($input) {{ $input }} @elseif ($blade_type === 'colorpicker') {{-- Widget-shaped inputs (colorpicker, datepicker, etc.) don't share the text-family prop shape, so dispatch them explicitly with only the props they accept. Avoids leaking type/input_icon/ maxlength/etc. as bogus HTML attrs on the widget's outer div. --}} @elseif ($blade_type === 'datepicker') {{-- $item->{$name} may be a Carbon (models that cast the column to `date`, e.g. License::purchase_date) or a plain string. Normalize to Y-m-d via strtotime so the datepicker JS can parse it. Without this, Carbon stringifies as "Y-m-d H:i:s", the picker fails to parse it, renders blank, and submit wipes the field. --}} @elseif ($blade_type === 'datetimepicker') @else @endisset

{{-- Optional col-md-1 sibling of the input column for a small action button (e.g. the "new" button next to a user select, or the wand generator next to the password field). Callers pass .... Matches the manager-picker layout in x-input.user-select. --}} @isset($after_input)

@endisset @if ($info_tooltip_text)

@endif {{-- Force the help block onto a new grid row regardless of how narrow the input column is. Without this, callers using narrow input_div_class values (e.g. col-lg-3 for a number + days addon) hit a case where label + input + help offset + help width sum to exactly 12, and the help renders beside the input instead of underneath it. --}}

{{-- Error + help wrapper. Fixed at col-md-9 col-md-offset-3 so the help text always has room to breathe on its own row, regardless of how narrow the input column is. Offset aligns under the input column (which sits after the col-md-3 label). --}}

@if ($help_text) {{-- $help_text is already HTML-entity-escaped by Blade's attribute-binding sanitize pass (:help_text="trans(...)" turns real double-quotes into " before the value lands here). Using {!! !!} outputs those entities as-is so the browser renders them as real characters. A plain {{ }} here would escape a second time (" -> "), which is what shows up as literal " in the page. --}} {!! $help_text !!} @elseif ($help_html) {{-- Raw HTML help — the caller has opted in, we render unescaped straight to the

. See the help_html prop docs above. Note: to pass a trans() string with HTML in it, use the static- attribute form help_html="{!! trans('...') !!}" — the dynamic-binding form :help_html="trans('...')" runs the value through BladeCompiler::sanitizeComponentAttribute() and turns your tags into <a> entities. --}}

@if ($help_icon) @endif {!! $help_html !!}

@endif