https://twill.io logo
Powered by
# ❓questions
  • l
    yes, the published work fine thanks
  • d
    hello
  • d
    is there a way to prevent people from uploading unsupported medias?
  • d
    they keep uploading SVG then ask why it doesn't work
  • d
    Also how do you collapse a fieldset by default?
  • d
    I have a lot of fieldsets on a page and I want them closed
  • d
    I tried @formFieldset(['id' => "homepage-questions", 'title' => 'Questions', 'open' => false]) and it's still closed
  • i
    Hi @delta107 you can configure twill to support SVG if needed. If you want to prevent uploads there's 
    twill.media_library.allowed_extensions
  • d
    thnx
  • i
    Copy code
    @section('fieldsets')
    <a17-fieldset title="Another section" :open="false">
       // fields here
    </a17-fieldset>
@stop
  • i
    the open option is not exposed on the blade component, it definitely should!
  • d
    What folder are the @directives?
  • d
    not sure where to search as I couldn't find them
  • d
    hmm but do you guys avoid @formFieldset directives in-house?
  • d
    are the @directives harder/less-efficient to use than components directly?
  • p
    I personally always reach for 
    @form...
    directives, unless I absolutely can't
  • i
  • i
    directives are of course preferred, but if the blade file behind the directive doesn't give access to a prop of the Vue component, using the Vue component is fine, though it could change in the future.
  • i
    that's why I was saying we should add the open prop to the blade file
  • d
    oh so you use the @directives as sort of an interface for compatibility? like a wrapper
  • i
    yes
  • d
    ok good to know
  • d
    but one thing I was wondering is is it possible to make changes to the TwillServiceProvider without touching vendor folder?
  • i
    not without a composer override, but what are you looking to change? You might be able to do it from your own service provider
  • d
    ok thanks, I was looking to patch in the singleton PR but I see it's way way too much trouble
  • d
  • i
    this will be released asap
  • d
    what is the recommendation for naming pivot (many-to-many) tables? I created a table 
    category_products
    (linking 
    categories
    and 
    products
    ) and everything works correctly until i add this to my 
    CategoryRepository
    Copy code
    public function getFormFields($object)
    {
        $fields = parent::getFormFields($object);
        $fields['browsers']['products'] = $this->getFormFieldsForBrowser($object, 'products');

        return $fields;
    }
    it is looking for 
    category_product
    instead, which i don't understand
  • p
    Not sure if it's to be considered a "convention" but I think I would recommend following the Laravel docs for this kind of thing: https://laravel.com/docs/8.x/eloquent-relationships#many-to-many-table-structure So a pivot for 
    users
    that belong to many 
    roles
    would be 
    role_user
  • d
    ah, so singular for both
1...130131132...484Latest