I feel there will be more developer control... if all the files are readily available at their specific folders. For example, config/twill.php with all values instead of being empty... similarly, all index, show, edit, create files in the view folder... it becomes a lot easier just edit and see the output... instead of searching or finding out ways to modify these files... keep all the files in the /app/ folder may increase the adoption i feel..... Would like to know if this was a planned approach and why...

Everything you're asking for is already possible through Laravel features which Twill is not preventing you to use: you can publish the whole config if that's what you're after, but it's not recommended. You can publish all views too, but then you're on your own to maintain them.

Hey! I found in the Twill doc custom validations messages, but I have no idea how exactly I can use them, can someone help me? Or I like to use the predefined ones in the translation file. The main thing is that the validation error is displayed at the form field.

hey @xbille do you mean you'd like to translate them? Or change the English version too?

I want to use them directly on the form field. 🙂 It works great for individual rule classes, but not for standard rules like 'required'.

you can edit this default Laravel file in your application too

I have seen this files, thank you. 🙂 But I want to use them in default validation like required. Currently the validation error is displayed at the bottom and not like custom validation directly at the form field.

like here ... the Page Type field is required.

oh, in the create modal, ok, that makes sense. well it's not supported there at the moment

in the form what you describe would work

not only in the modal, also in update form 🙂

well that field is still in the modal

if you put it on the form the error will show next to it

or do you mean for the color field here?

how do you set that validation rule in the form request?

At the second example the color field is not in the modal 🙂

yeah got it, can you share your form request class?

I think i can use the $this->messagesForTranslatedFields() method? but how? 😅

thanks, yes, inside of the

messages

function

okay thanks and how I can integrate the function?

I'm not sure what you mean. Laravel form requests have a messages function that you can implement. In there, you can call Twill's helper and return it's result

can you show me an example please?

for my code .... dont work 😦

Directly on the field validation isn't laravel specific it's the HTML5 validation tho. where HTML5 will not submit a form if something required isn't filled, or a type="email" input doesn't seem to have an email string in there etc

@xbille you need to call the helper. I'm on mobile right now so can't share a nice snippet but basically return

$this->messagesForTranslatedFields(...)

inside of

messages

i try 😅