I
I
Ilya2018-06-10 14:56:15
Laravel
Ilya, 2018-06-10 14:56:15

What happened to laravelcollective after the update?

It is not clear what happened to laravelcollective after the update: composer update
Previously, if the url had the ?group_id=2 parameter, the select field correctly displayed the current value

{{ Form::label('group_id', 'Группа') }} 
{{ Form::select('group_id', [1=>'group1', 2=>'group2', 3=>'group3'], null, ['id' => 'group_id', 'class' => 'app-input__select form-control']) }}

Let 's say shop.local/admin/product/create/?group_id=2
The form showed the current value = group2. Now, like a grandmother whispered.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
V
Victor, 2018-06-10
@flammerman

https://github.com/LaravelCollective/html/issues/531
I removed this behavior by default, because many users did not like it, now you need to enable it through The package is supported somehow, so they will then score on the repository for a year, then they rake up PR in a crowd, then they forget to transfer the functionality from the old branches to the new ones.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question