refactor(grids): cleanup search snippets

[damyanpetev]

lastSearchInfo.matchInfoCache.length -> lastSearchInfo.matchCount and removed the check for the entire object since that does nothing
Matching samples PR IgniteUI/igniteui-angular-samples#3496

Checklist:

• check topic's TOC/menu and paragraph headings
• Include TOC topic labels in topic content has a valuable update, it's new or considered as preview\ beta
• link to other topics using ../relative/path.md
• at the References section at the end of the topic add links to topics, samples, etc
• reference API documentation instead of adding a section with API

• use valid component names - [Data] Grid, IgxSelectComponent, <igx-combo>
• use spell checker tool (VS Code, Grammarly, Microsoft Editor)
• add inline code blocks for the names of classes / tags / properties
• add language descriptor for the code blocks
• check broken links (use browser add-on)
• check if sample is working and fully visible in the topic
• check if sample is working and fully visible in the StackBlitz
• check if code blocks match the code in StackBlitz demo

• follow SEO guidelines to fill topic's metadata (SEO guidelines)

• do not resolve requested changes (leave that to the reviewer)
• add pending-localization label when the review of the PR is done
• add a member from the localization team to translate it

The base branch was changed.

[Copilot]

Pull request overview

Updates the Grid search documentation snippets to reflect a refactored search API surface by switching from lastSearchInfo.matchInfoCache.length to lastSearchInfo.matchCount, and simplifying the sample templates accordingly.

Changes:

• Replace usage of lastSearchInfo.matchInfoCache.length with lastSearchInfo.matchCount in results-count snippets.
• Remove the outer *ngIf="@@igObjectRef.lastSearchInfo" wrapper in results display snippets (across EN/JP/KR docs).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 6 comments.

File	Description
kr/components/grids_templates/search.md	Updates search result count snippets to use matchCount and adjusts template conditions.
jp/components/grids_templates/search.md	Updates search result count snippets to use matchCount and adjusts template conditions.
en/components/grids_templates/search.md	Updates search result count snippets to use matchCount and adjusts template conditions.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The template now accesses @@igObjectRef.lastSearchInfo.matchCount without guarding lastSearchInfo. If lastSearchInfo is undefined before the first findNext/findPrev call, Angular will throw when evaluating the *ngIf expressions. Consider restoring the *ngIf="@@igObjectRef.lastSearchInfo" guard or using the safe-navigation operator (e.g., lastSearchInfo?.matchCount).

[Copilot]

Inside the igx-suffix block, @@igObjectRef.lastSearchInfo.matchCount is used without guarding lastSearchInfo. If searchText is pre-populated (or findNext hasn’t run yet) this can still evaluate with lastSearchInfo undefined and cause a template error. Guard lastSearchInfo or use safe navigation.

[Copilot]

@@igObjectRef.lastSearchInfo.matchCount is referenced without checking lastSearchInfo first. If lastSearchInfo is undefined before the first search, Angular will throw when evaluating the *ngIf expressions. Consider adding back an *ngIf="@@igObjectRef.lastSearchInfo" guard or using safe navigation (lastSearchInfo?.matchCount).

[Copilot]

In this snippet, @@igObjectRef.lastSearchInfo.matchCount is accessed without guarding lastSearchInfo. Even though the suffix is shown when searchText.length > 0, lastSearchInfo can still be undefined (e.g., when searchText is set programmatically before running findNext). Guard lastSearchInfo or use safe navigation.

[Copilot]

@@igObjectRef.lastSearchInfo.matchCount is used without guarding lastSearchInfo. If lastSearchInfo is undefined before the first findNext/findPrev call, Angular can throw while evaluating these *ngIf expressions. Consider restoring the *ngIf="@@igObjectRef.lastSearchInfo" guard or using safe navigation (lastSearchInfo?.matchCount).

[Copilot]

Within the igx-suffix block, @@igObjectRef.lastSearchInfo.matchCount is accessed without guarding lastSearchInfo. If searchText is initialized programmatically and findNext hasn’t executed yet, this can still error. Guard lastSearchInfo or use safe navigation.