Twill

So your custom component is under frontend/js/components/customs/?

Hi. Is it possible to make a connected fields in repeater by using field value from block?

Hi, that sounds a bit tricky, i don't think so

For example I have select in block and I want to show/hide some fields in repeater of this block depends on value of this select 🙂

Just tried to add 'connected_field' construction in repeater and tried to use value from block, but nothing(

Maybe I could somehow access parent block variable in repeater and use it?

yeah that's what I'm looking into, we would need to add a new option to the connected field to let you indicate that the field you're looking to base the condition on is in the parent block not the current block (repeater in your case, but repeaters are blocks technically)

so right now it is definitely not supported

And we're a bit afraid of it being a bit dangerous

what you could do is use 2 repeater types, but when changing the select value you'd loose your repeater items

depending on what you're looking for that could be fine

see what I mean? That'd be having the connected field in the block, not the repeater

Okay. I see. Thank you very much. Do you have a plan to implement that new option for connected fields between repeaters and normal blocks in the future?)

Going into a thread to make it easier 🙂

like, this should work 🤦‍♂️ 😄 when you save a vue file does the browser reload?

and i got the shell error, i will rerun the dev mode with the env var

the missing manifest exception was caused because i missed the http:// on the TWILL_DEV_MODE_URL env variable

i changed it as in the documentation and works like charm

ok, i rerun the dev mode, npm server works, page works, hot reload not working

if i change the component in the vendor folder, npm rebuilds the files, it i modify the component in my assets folder, i got this error in console:

meanwihile the ws connection is ok in the browser

I dont know what's different honestly 😄

Hmm, I had also some issues before so I skipped this builder and manualy started build command to check what was the issue. You can try it too.

that is exactly what i do, but i have the console error 😦

i run the commands in the container, but i will try it in the host machine

yeah, i got the console error for missing componen

I really do not know any other thing to try. It might be because of docker in between. I run everything locally.

i used before npm watcher for vujs in docker and it worked, i dont know why it does not work now

in which js file should be the component?

if you use twill:build (and disable dev mode) you do are able to render the component?

I think from Twill perspective is that we dont have STDOUT hooked into our output, only STDERR on fail. This could be implemented trough a new argument. `Process` component supports this.
It can be implemented via argument `--output` so we see can where nodejs failed.
https://github.com/area17/twill/blob/2.x/src/Commands/Build.php#L138-L146

like the building process does not takes the component for building

<@1005027989009997834> can you check my previous message?

yes, i misstyped, i tried the build command not dev

🔥 Building Twill assets in production mode.
Loading components from: @/components/customs/
⠦  Building for production...
 WARNING  Compiled with 12 warnings

hold up.. you are in a custom page, can you try to put <a17-hello-world .. in a form instead.

so we can use these components in a form?

here is wanted to create a "full page" custom vuejs component

not sure if this will work, you can try adding 

```
@push('extra_js_head')
    @if(app()->isProduction())
        <link href="{{ twillAsset('main-form.js') }}" rel="preload" as="script" crossorigin />
    @endif
@endpush
``` 

to your custom page.

if that does not work, please create an issue than I can look into it.

no, unfortunately it does not work outside of a form

i will create a github ticket for it, thank you for your support!

that's interesting, we definitely have users with custom components on free pages

https://discord.com/channels/811936425858695198/915610590104387584/915677751720169483

we can definitely improve this now that there's an issue for it, but check out the link, that solution should work

ok, i have something more complex here 😄

i wanted to user the listing from the crud

and the component will be used for editing selected entity

i am using the edit method from the controller, but the layout extends the free layout

i tried that in a custom cms page, like pboivin in the previus thread, but it still does not work

i don't understand what you mean by "use the listing", are you trying to use our Vue components that are powering the index table?

if you want to use any custom Vue component from a free page, you need to override the free page layout

https://discord.com/channels/811936425858695198/811986149064441927/1020257143477256193

so in this screenshot it should be using a custom layout, not twill::

yes, you are true, the overriding and changing the free layout worked

this is the edit blade, which is properly loaded in a browser, but the component missing

i'm confused about how can i make a custom user with custom roles

in the docs they are referencing creating a profile for the user

Hi I think you're reading the wrong section

https://twill.io/docs/guides/adding-custom-roles-and-permissions.html#context

the guide with breeze is for your frontend users

<@1016609822923313244> you can use this link and type the email of the user. In Twill 3 you can do it from the user form in the CMS, but for now that's how you'd do it.

i think clients wouldn't be happt with that

why i can't show password in the admin for users ?

and i added the password and the email one of them will be shown !