refactor: use 'basicSelector' for maxWidth

[mkilpatrick]

No description provided.

[github-actions]

Warning: Component files have been updated but no migrations have been added. See https://github.com/yext/visual-editor/blob/main/packages/visual-editor/src/components/migrations/README.md for more information.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 131a11c3-24af-4d5b-b408-3a6f5180fd35

📥 Commits

Reviewing files that changed from the base of the PR and between 3ae2db9 and 01d2aa7.

📒 Files selected for processing (5)

• packages/visual-editor/src/components/footer/ExpandedFooter.tsx
• packages/visual-editor/src/components/header/ExpandedHeader.tsx
• packages/visual-editor/src/editor/MaxWidthSelector.test.tsx
• packages/visual-editor/src/editor/YextField.test.tsx
• packages/visual-editor/src/editor/YextField.tsx

💤 Files with no reviewable changes (1)

• packages/visual-editor/src/editor/YextField.tsx

---

Walkthrough

This pull request refactors the maxWidth field handling across the visual editor components. The dedicated "maxWidth" field type is removed from the YextField component, and components that previously relied on this built-in type (ExpandedFooter and ExpandedHeader) now define maxWidth using basicSelector with options dynamically generated by a new getMaxWidthOptions() utility function. Tests are updated to validate the new option generation logic.

Possibly related PRs

• refactor: merge dynamicSingleSelect into basicSelector #1158: Performs the same code-level refactor of collapsing a specialized selector type into the generic basicSelector, including edits to YextField.tsx and test updates.
• refactor: add 'ctaSelector' fieldType #1170: Modifies how YextField handles specialized field types by extracting custom logic (CTA) into a separate handler, similar architectural change.
• refactor: remove text from YextField #1182: Executes the same refactor pattern by removing a dedicated field type branch ("text") from YextField and updating callers to use native selector variants instead.

Suggested reviewers

• briantstephan
• jwartofsky-yext
• benlife5

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided by the author, making it impossible to assess the intent or context of the changes.	Add a description explaining the purpose and motivation for refactoring maxWidth to use basicSelector instead of a dedicated type.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main refactoring change: converting the maxWidth field implementation to use basicSelector.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch max-width

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[jwartofsky-yext]

LGTM!