Pedro Martins

@rabol hey \o nice to see you here. I think we have 3 reasons for keeping the `wrapper` in custom_html field. I will try to rephrase what me and @tabacitu...

None of backpack fields uses `field_wrapper` naming convention, but they all support it. In my understanding, the wording here is: `Backpack wraps your field with a custom wrapper that you...

I converted this into two PR's. https://github.com/Laravel-Backpack/PRO/pull/86 and https://github.com/Laravel-Backpack/CRUD/pull/4625 Closing in favor of keeping any discussion regarding this in https://github.com/Laravel-Backpack/CRUD/pull/4625

@niladam for a field you validate with: `'repeatable.*.field_name'=> 'required'` you can put in your messages: `repeatable.*.field_name.required => 'this field is required'`. The PR that works on this is: https://github.com/Laravel-Backpack/CRUD/pull/4220/files but...

I think this is done. 👍 I've just tested repeatable messages and everything is displaying correctly. This was a misunderstanding on how to display repeatable messages. I am closing this,...

@tabacitu As you can see, you can't do it like that either! Request will have `relationB => null` because the field is empty. That would do the same I described,...

Hello @otradnix Thanks for the contribution. We use it with a default value of "users" but probably we can add it on permission file too. Did you try adding that...

Hey there @otradnix Simple things make the life of a lot of people better. I think you are right in the point that we don't have it in the permission...

Hello @AbbyJanke hope you are doing fine 👍 I have this issue on my back to close 4.1 board, I know it's old but anyway, if you re-call what this...

As you are changing config values, is it possible you are still using cached values? Would you mind trying `php artisan config:cache` ? BR