Make it possible for the site search input field to have different values for "name" and ID

[yvonnetangsu]

READY FOR REVIEW

Summary

• Currently, in the site search component search input field, the "name" attribute and ID are forced to take on the same value (variable search_input_name), but on some sites when there are multiple instances of the search form, sometimes we need 2 forms with the same "name" for the input fields but different IDs.
• This PR adds the option to add a different ID search_input_id when needed. If that's not provided, it will be the same as the value for "name"
• Note: There might be a different approach to this - do we need the search input field to have an ID at all? If not, perhaps we can remove it and just add an additional_input_attribute variable in the next Decanter version.

Needed By (Date)

• Sooner the better

Urgency

• N/A

Steps to Test

1. Copy the content of site-search.twig and paste the content into a test.twig (needs to create this file) file in the developer folder and follow the README there to set up the preview environment.
2. Add test.json file in the developer directory with different search_input_name and search_input_id values.
3. Do npm run dev and npm run start. Look at the site search component on the rendered page in the inspector and verify that the ID and name for the search input field are different.

Affected Projects or Products

• Decanter
• D8
• Redwood

Associated Issues and/or People

• Make it possible for site search component input field to have different name and ID values #686

[sherakama]

Thanks for this.

[sherakama]

This keeps it backwards compatible but we should remove it in version 7 and just go with the two separate ids.