SuperSelect - docs for search position (HDS-4254)

[KristinLBradley]

📌 Summary

If merged, this PR adds documentation for the SuperSelect searchFieldPosition feature.

• Web docs: https://hds-website-git-hds-4254-super-select-search-p-2680bc-hashicorp.vercel.app/components/form/super-select

Related:

• Component PR: SuperSelect - search position (HDS-4254) #2612

🔗 External links

• Jira ticket: HDS-4254

---

👀 Component checklist

• [ ] Percy was checked for any visual regression
• [ ] A changelog entry was added via Changesets if needed (see templates here)

💬 Please consider using conventional comments when reviewing this PR.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
hds-showcase	✅ Ready (Inspect)	Visit Preview	Jan 23, 2025 7:05pm
hds-website	✅ Ready (Inspect)	Visit Preview	Jan 23, 2025 7:05pm

[KristinLBradley]

@majedelass Do you think any of the illustrations or design related docs need updating? I didn't see anything obvious when I looked through but wanted to double-check.

Web docs preview: https://hds-website-git-hds-4254-super-select-search-p-2680bc-hashicorp.vercel.app/components/form/super-select

[Dhaulagiri]

I would think 4.16

[jorytindall]

I went down the rabbit hole with #2612 to better understand where this content was coming from, and I personally found it a bit confusing to read through. Given the context it looks like we're documenting another argument along with the rest of the component API, but the note about it not being possible to override kind of makes this prop useless to consumers. That is, unless we determine that it's useful for consumers to know that we are setting this argument explicitly for accessibility reasons being that it's coming from PowerSelect.

At a minimum it might be helpful to make that more clear immediately in the component API (leading with the content about not being able to override it and why), then capturing the rest of the details about the property if necessary.

Not overly opinionated on the topic and I don't have all of the background, just noting a couple of thoughts.

[jorytindall]

I removed documentation for renderInPlace and ``searchFieldPosition` within the API docs properties list and added mention of them within an existing related Info banner.

@KristinLBradley personally, I think this is a better solution than including them in the component API list which seemed to create a bit of a false equivalency. Thanks for making this change, curious what other folks think!

[majedelass]

This looks good. I removed the warning within the guidelines about the nested interactive of the previous version.

[shleewhite]

website changes look good! But why are there changes to yarn.lock?

[dchyun]

With the new changelog scripts I think these updates can be removed, as they'll be generated later.