Skip to content

Conversation

@raphael-geffroy
Copy link
Contributor

Q A
Bug fix? no
New feature? no
Docs? yes
Issues Fix #3057
License MIT

@carsonbot carsonbot added the Status: Needs Review Needs to be reviewed label Sep 18, 2025
@carsonbot carsonbot changed the title docs: document possibility to disable tomselect default plugins docs: document possibility to disable tomselect default plugins Sep 18, 2025
@Kocal Kocal added Documentation Improvements or additions to documentation Autocomplete labels Sep 19, 2025
@carsonbot carsonbot changed the title docs: document possibility to disable tomselect default plugins [Autocomplete] docs: document possibility to disable tomselect default plugins Sep 19, 2025
@Kocal Kocal changed the title [Autocomplete] docs: document possibility to disable tomselect default plugins [Autocomplete] Document how to disable default TomSelect plugins Sep 19, 2025
Copy link
Member

@Kocal Kocal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution!

Comment on lines 209 to 219
You can disable default plugins using ``tom_select_options.plugins``::

$resolver->setDefaults([
'class' => Ingredient::class,
'tom_select_options' => [
'plugins' => [
'clear_button' => false, // Disable the clear button
'remove_button' => false, // Disable the remove button
],
],
]);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest a new dedicated section describing: why these plugins are added by default, and how you can describe them

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe a small dedicated section yep

And without a minimal explaantion on the "why" (let's maybe add a link to their documentation) ?

😅

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So how can we move forward here ? @raphael-geffroy you think you could add a first version of the section / paragraph suggested by @Kocal here ? If not, i'd suggest we merge this PR and open an issue for anyone to controbute ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll have a look at it this week-end, thanks !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Autocomplete Documentation Improvements or additions to documentation Status: Needs Review Needs to be reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Autocomplete] Document default plugins can be disabled

4 participants