Package laravelcollective/html is abandoned, you should avoid using it. Use spatie/laravel-html instead

@LaryAI

Thanks for your reply.

If I want to use ""Form" Facade for spatie/laravel-html, what should I add in 'aliases' ?

@hiviyan Don't take Lary's answer too literally. As often happens its a confusion of bits of code scraped from unrelated sources.

The Spatie html package has a completely different syntax to Laravel Collective

Bear in mind that these are convenience helpers. They are marginally simpler than writing the html yourself.

@Snapey Thanks!

@LaryAI @LaryAI How can we add aliases in Laravel 11.x version? Kindly suggest. Thanks.

@tykus Thanks!

@tykus This package, on the other hand, has helped me so much, because to write the selects, it saved me from writing so much html code...

{{ Form::select('id_console', array('' => 'Select console') + $console, $article->id_console?? '',  array('class' => 'form-select')) }}

instead of writing:

        <select class="form-select" name="id_console[]" id="id_console" multiple>
          @if(empty($article->id_console))
            <option value="0">Select Console</option>
            @foreach($consoles as $console)
              <option value="{{ $console->id }}">{{ $console->abb_cat }}</option>
            @endforeach
          @else
            <option value="0">Select Console</option>
            @foreach($consoles as $console)
              <option value="{{ $console->id }}"
                @foreach ($list_consoles as $list_console)
                  @if($console->id == $list_console->id)
                    selected="selected"
                  @endif
                @endforeach
                >{{ $console->abb_cat }}</option>
              @endforeach
            @endif
          </select>

Maybe there is a way to simplify the html of the select, however, the laravelcollective/html package helped a lot.

@Xanger For me, i can't understand what this actually to do, unreadable :)

{{ Form::select('id_console', array('' => 'Select console') + $console, $article->id_console?? '',  array('class' => 'form-select')) }}

create a blade component instead, blade component more powerful

@hiviyan Most of us use regular html in blade, and some create reusable blade components (which is still regular html in blade but in a component).

@Tray2 Thanks for your input!

@hiviyan spatie/laravel-html have awful documentation. In most cases you will need to go in source files to understand how to do something even not mentioned in documentation. Even simplest questions you will not find in documentation (like how to add size of text area)... {!! html()->textarea('description', null)->class('form-control')->rows(3)->cols(50) !!} or something like following: {!! html()->modelForm($customMetric,'PATCH', route('data-source-fields.updateCustomMetric', [$dataSource->id, $customMetric->id]))->id('edit-custom-metric-form')->class('fields-form-inline')->open() !!}

Most of time you will spend exploring source code of larael-html cause lack of good documentation.

github.com/spatie/laravel-html

@vincej

Does anyone know of a programmatic approach to changing Collective to raw HTML?

The legacy codebase I work used Collective heavily, I've been in the process of creating components for the different inputs and then gradually switching them all over

@cwhite Thanks for that. Could you elaborate a little on, maybe with an example : " creating components for the different inputs "

Many thanks!

@vincej,

Sure, essentially you want to abstract away a lot of the duplication and styling

components/form/index.blade.php

@props([
    'method' => 'post',
    'model',
])

@php
    $method = strtoupper($method);

    $formMethod = in_array($method, ['GET', 'POST'], true)
        ? $method
        : 'POST';
@endphp

<form
    method="{{ $formMethod }}"
    {{ $attributes }}
>
    @unless ($method === 'GET')
        @csrf()
    @endunless
    @unless ($method === $formMethod)
        @method($method)
    @endunless
    {{ $slot }}
</form>

I use it as follows:

<x-form
    method="get|post|put|patch..."
    :action="route('...')"
    :model="$model" // any arrayable (optional)
>
// content or other form inputs
</x-form>

The input component are similar, I have base components (like for the input tag) and then other components that build off the base component:

E.g., my text input just defers to the base input component

<x-form.input
    type="text"
    {{ $attributes }}
/>

I use them in the following way:

<x-form.text
    name="username" // if no value is passed and the form has an arrayable model,
                   // then uses this to get value from model attribute or array key
    id="..." // if no id is passed then assumed to be same as name
    label="Username" // automatically creates a label (using label component) 
                // above the input and associates with this input
    required // optional attribute, label component automatically adds red asterisk
              // when input is required
    value="..." // when no value is passed then uses name and model to get input
               // (can also handle old input)
/>

The components are also capable of showing validation errors under each input automatically (using the name attribute)