Twill

great! I'll use textarea for now, but I will want of course when I get the time to integrate something besides quill

I've often seen the need to inject classes in the tags generated by the text editor

I know tinyMCE has some options for injecting classes into generated tags

there's the option to use tiptap as well. but overall we're not satisfied with our wysiwyg fields situation at the moment and are planning to address it soon

I try to use custom repeaters for my project, but the vue component doesn't render on my view. Can someone help me?

Hi <@370485710710505473> can you share more about what you're trying to achieve and the steps you took for now? I would recommend building a field that you put inside of a regular repeater field instead of rebuilding repeaters, unless you're looking to add functionality to our repeaters?

Oke forget the custom repeaters question. So the only thing I actually want is to render the custom vue component block I have added in the following location /js/repeaters/CustomBlock.vue

I followed this guide: https://spectrum.chat/twill/tips-and-tricks/adding-a-custom-block-to-twill-admin-view-with-vuejs~028d79b1-b3cd-4fb7-a89c-ce64af7be4af

right, so at the moment I think you're just running into a conflict with an internal component

I have only added a vue component, added this in my twill config: 'custom_vue_blocks_resource_path' => 'js/repeaters'

and using the vue directive in my homepage.blade.php file like so:     <a17-block-item name="name"></a17-block-item>

https://github.com/area17/twill/pull/1164

is the pathname correct? custom_vue_blocks_resource_path

yes this all seems correct, though if this is for a custom field, you can use a custom component instead of a custom block, as I just explained in <#811986149064441927>

well you didn't share the code of the js file that is causing an issue, so for now I'm not sure. Just to check, you are running php artisan twill:build ?

<template>
    <div class="block__body">
        test
    </div>
</template>

<script>
import BlockMixin from '@/mixins/block'

export default {
  mixins: [BlockMixin]
}
</script>

and I am running the twill command outside of docker tho

'blocks' => [
        'test' => [
            'title' => 'Item',
            'trigger' => 'Add item',
            'components' => 'a17-block-test',
            'compiled' => true
        ],

the first step would be to make sure your code ends up in the bundle the page is loading

we use the vue devtools, but the custom block component is not being rendered

Put a random string in the source of the component and search for it in the build?

then your problem is that you're not building correctly

is this valid?     'custom_vue_blocks_resource_path' => resource_path('js/blocks'),

it is already relative to resource path so no

I followed this https://spectrum.chat/twill/tips-and-tricks/adding-a-custom-block-to-twill-admin-view-with-vuejs~028d79b1-b3cd-4fb7-a89c-ce64af7be4af

'custom_vue_blocks_resource_path' => 'js/repeaters',
'repeaters' => [
    'item' => [
        'title' => 'Item',
        'trigger' => 'Add item',
        'components' => 'a17-block-item',
        'compiled' => true
    ],
],

 this is my twill.php

Can you publish the twill views to the project folder to override them? I mean obviously I can copy them, but will the override work? Thanks

Yes you can override them like any Laravel package using the vendor folder in your own views folder, but I do not recommend publishing all of them as this will mean you will have to keep them updated to upgrade Twill on your project.

Thanks <@!479379745856028705> ! Thanks for all your answers, it's very nice!

So I tried to remove the description field from the module migration but apparently there is some kind of validation behind the scenes that I can't find, yet it doesn't look like description should be mandatory

yet the admin panel complains about validation when you remove it

One more of those idiotic questions: if you do php artisan twill:make:module -BTP is it necessary to add -M if you want to have images in the block?

hmm outside of the fillable there should be nothing preventing you from removing description

you don't need -M in that case, blocks are medias capable by default

Also there is a misleading thing on https://youtu.be/9ZVtVTT7Jb4?t=50. I just checked and if you don't use with('blocks') the blocks will not load

yeah the video should use with('blocks') otherwise the relationship to blocks will not be loaded

I mean it's not a big deal, just a suggestion

thing is the project doesn't need blocks to be loaded when displaying all contributors so why load them?

Hi, I have such a menu but the primary navigation does not appear, does anyone know why?

the key at the first level should be real

all CRUD operations inside the module are working but the navigation is not visible.

since that's the route prefix of your realEstates module

yes, but there is another module that I use exactly the same way, it works.