EntitySearchInput should be able to be initialized automatically like other PrestaShop components

[jolelievre]

Prerequisites

• I understand and accept the project's code of conduct
• I have already searched in existing features request and found no previous suggestion of this feature.

Is your feature request related to a problem?

In PS 178 and even in 80 we introduced a EntitySearchInput js component, for now it is always initialised with explicit instanciation in the JS code. To ease the modules developer work this should be doable like other components relying on the initComponents method

Describe the solution you'd like

Here is the expected solution:

• add an option in the form type automatic_init false by default (naming should be improved)
• when this option is set we automatically add a dedicated class that can be used as a selector
  in the PrestaShop initComponents we can add a AutomaticEntitySearchInput its role is to select the inputs by class and then loop through each one of them to get their IDs (already automatically created as well)
• it needs to create a new EntitySearchInput for each element because the JS component was only built to target ONE input so far, and I’m not sure a refacto to handle multiple ones is necessary for now

Alternatives you've considered

Instead of creating a new AutomaticEntitySearchInput component which would only be used for the initComponents method, we can do a small refacto of EntitySearchInput :

• the first parameter which is a selector would be nullable
• if it's undefined/null then we use a default class selector as a fallback
• we refacto the initialization part a bit so that it can handle selector for single and/or multiple elements

We'll need to think about how this automatic initialization is handled in the form type, should it be the default behaviour (then we should modify all the current uses) or should the automatic initialization be activated manually (thus it won't impact the current use cases).

Additional context

No response

Do you plan to work on this feature?

• I'm willing to contribute a formal specification.
• I'm willing to provide any wireframes or design assets required for this feature.
• I'm willing to submit a Pull Request that implements this feature.
• I'm willing to help verify that the implemented feature works as intended and produces no unintended side effects.

[AureRita]

Hi @jolelievre ,

Thank you for your suggestion. The Maintainer Team will take it into consideration for future developments.

Please be aware that there is no guarantee that this feature will be developed anytime soon.
We're waiting for your PR 🚀

Thank you