chore: merge main into branch

[asanehisa]

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]

Walkthrough

This patch release (1.3.2) adds support for the comingSoon flag in hours-related UI components across the Locator and nearby locations features. The package version is bumped, changelog and Turkish locale strings are updated, and a new test case validates the comingSoon rendering behavior. Component hours props are refactored to remove type casting and pass object spreads directly. Additionally, field selection scoping and directory grid normalization logic are refined to handle source fields and incoming mappings more precisely.

Possibly related PRs

• yext/visual-editor#1215: Fixes embedded field picker scoping in mapping via updates to EmbeddedFieldStringInput.handleFieldSelect resolution path and document selection logic.
• yext/visual-editor#1226: Adds the same version 74 comingSoon fixture and modifies LocatorResultCard hours rendering behavior.
• yext/visual-editor#1220: Updates EmbeddedFieldStringInput callback argument handling and DirectoryWrapper grid normalization in parallel with this PR.

Suggested labels

create-dev-release

Suggested reviewers

• benlife5
• mkilpatrick
• briantstephan

🚥 Pre-merge checks | ✅ 2 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title 'chore: merge main into branch' is unrelated to the actual changeset. The PR contains multiple meaningful feature and bug fix changes (version bump, comingSoon handling, localization updates, component refactoring), but the title falsely describes it as a merge commit.	Update the title to reflect the actual changes, such as 'chore: v1.3.2 release with comingSoon UI enhancements and bug fixes' or similar.
Description check	❓ Inconclusive	No description was provided by the author, making it impossible to verify relevance to the changeset.	Add a pull request description that explains the purpose and scope of the changes included in this release.

✅ Passed checks (2 passed)

Check name	Status	Explanation
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 merge-main

---

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

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

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/visual-editor/src/components/Locator.test.tsx (1)

1186-1215: ⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicate test case.

This test case is identical to the one already added at lines 364-394. Having duplicate test entries in the array will cause redundant test execution and potential confusion.

🔧 Proposed fix

Remove this duplicate test case entry (lines 1186-1215) as it's already defined at lines 364-394.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/visual-editor/src/components/Locator.test.tsx` around lines 1186 -
1215, Remove the duplicate test entry object whose name is "version 74
comingSoon" (the case with document.comingSoon: true, version: 74, and props: {
...LocatorComponent.defaultProps }) — it is already defined earlier in the
tests; delete this second occurrence to avoid running redundant tests and keep
the test array unique.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@packages/visual-editor/locales/platform/tr/visual-editor.json`:
- Line 568: The translation for the key linkedEntityMultiValueWarning has
inverted meaning; update the Turkish string so it clearly states that the first
linked entity will be used as a fallback (not that it won't be used). Edit the
value for linkedEntityMultiValueWarning to a wording like "{{linkedField}}
birden fazla bağlantılı varlık içeriyor; {{resolvedField}} için ilk olan
kullanılacak." so it accurately reflects the fallback behavior.

---

Outside diff comments:
In `@packages/visual-editor/src/components/Locator.test.tsx`:
- Around line 1186-1215: Remove the duplicate test entry object whose name is
"version 74 comingSoon" (the case with document.comingSoon: true, version: 74,
and props: { ...LocatorComponent.defaultProps }) — it is already defined earlier
in the tests; delete this second occurrence to avoid running redundant tests and
keep the test array unique.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: cfa7e1b8-b0e7-4154-b4b2-ccc6c759cac3

📥 Commits

Reviewing files that changed from the base of the PR and between 1a1a504 and a50475c.

📒 Files selected for processing (8)

• packages/visual-editor/CHANGELOG.md
• packages/visual-editor/locales/platform/tr/visual-editor.json
• packages/visual-editor/package.json
• packages/visual-editor/src/components/Locator.test.tsx
• packages/visual-editor/src/components/LocatorResultCard.tsx
• packages/visual-editor/src/components/directory/DirectoryWrapper.tsx
• packages/visual-editor/src/components/pageSections/NearbyLocations/NearbyLocationCard.tsx
• packages/visual-editor/src/editor/EmbeddedFieldStringInput.tsx

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix inverted meaning in Turkish linked-entity warning.

The new sentence says “don’t use the first one,” which appears opposite of the fallback behavior this warning communicates. This will mislead users in the editor UI.

Suggested text correction

-  "linkedEntityMultiValueWarning": "{{linkedField}} birden fazla bağlantılı varlık içerir. {{resolvedField}} için ilkini kullanma.",
+  "linkedEntityMultiValueWarning": "{{linkedField}} birden fazla bağlantılı varlık içerir. {{resolvedField}} için ilkini kullan.",

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	"linkedEntityMultiValueWarning": "{{linkedField}} birden fazla bağlantılı varlık içerir. {{resolvedField}} için ilkini kullanma.",
	"linkedEntityMultiValueWarning": "{{linkedField}} birden fazla bağlantılı varlık içerir. {{resolvedField}} için ilkini kullan.",

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/visual-editor/locales/platform/tr/visual-editor.json` at line 568,
The translation for the key linkedEntityMultiValueWarning has inverted meaning;
update the Turkish string so it clearly states that the first linked entity will
be used as a fallback (not that it won't be used). Edit the value for
linkedEntityMultiValueWarning to a wording like "{{linkedField}} birden fazla
bağlantılı varlık içeriyor; {{resolvedField}} için ilk olan kullanılacak." so it
accurately reflects the fallback behavior.