fix fuzzy

[guitavano]

The default has to be empty

Summary by CodeRabbit

• Chores
  • Optimized search request parameter handling to improve efficiency by conditionally including the fuzzy search parameter only when applicable, reducing unnecessary payload overhead.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The default value of the fuzzy parameter in the intelligent search utility changed from "auto" to an empty string, and the parameter is now conditionally added to the request payload only when truthy, rather than being always present.

Changes

Cohort / File(s)	Summary
Fuzzy Parameter Default & Conditional Inclusion vtex/utils/intelligentSearch.ts	Changed fuzzy default from "auto" to "" and modified payload composition to conditionally include fuzzy only when truthy via spread operator

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A fuzzy logic twist, so neat,
From "auto" down to empty's beat,
Now only truthy values stay,
In payloads sent on search's way!
Cleaner requests, we celebrate—
Less chatter makes them lightweight! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is significantly incomplete, missing most required sections including a detailed explanation of changes, issue link, Loom video, and demonstration link.	Complete the description template by adding a detailed explanation of why the fuzzy default changed, link the relevant issue, and provide any supporting materials or demonstration links.
Title check	❓ Inconclusive	The title 'fix fuzzy' is vague and generic, using a non-specific term 'fix' without conveying what the actual change accomplishes or why it matters.	Provide a more descriptive title such as 'Change fuzzy default from auto to empty string' to clearly communicate the specific change being made.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

---

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.}

[github-actions]

Tagging Options

Should a new tag be published when this PR is merged?

• 👍 for Patch 0.133.23 update
• 🎉 for Minor 0.134.0 update
• 🚀 for Major 1.0.0 update

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

vtex/utils/intelligentSearch.ts (1)

70-70: Consider explicit empty string check for clarity.

The truthiness check (fuzzy ? { fuzzy } : {}) will exclude the parameter when fuzzy is any falsy value (empty string, null, undefined, etc.). While this works for the current use case, it could be more explicit.

If the intent is specifically to exclude empty strings, consider:

🔎 More explicit alternative

-  ...(fuzzy ? { fuzzy } : {}),
+  ...(fuzzy !== "" ? { fuzzy } : {}),

This makes it clearer that you're specifically handling the empty string case, though the current implementation is also acceptable.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 30ca287 and 3cbde8b.

📒 Files selected for processing (1)

• vtex/utils/intelligentSearch.ts

🔇 Additional comments (1)

vtex/utils/intelligentSearch.ts (1)

61-61: No action required—the fuzzy parameter change has no functional impact.

The default value of fuzzy changed from "auto" to "". Combined with the conditional inclusion on line 70, the fuzzy parameter is now omitted from requests when not explicitly provided. According to VTEX Intelligent Search API documentation, when fuzzy is not included in the request, the API applies its default fuzzy matching behavior automatically (based on query term length: 1 for 3–5 characters, 2 for 6+ characters). This behavior is identical to explicitly sending fuzzy="auto", so there is no change in search result behavior. All five call sites rely on the default value and will continue to work as expected.