fix(tablev2): replace JSON.stringify with per-column String() matching in globalFilter

[eve-scality]

Summary

Fixes false-positive matches in the TableV2 global filter caused by JSON.stringify(row.values) serializing the entire row object — including JSON structural characters ({, }), column ID keys (e.g. firstName), and full ISO-8601 date strings with milliseconds — as searchable text.

The fix replaces JSON.stringify(row.values) in stringifyFilter with a per-column iteration over columnIds, calling String(row.values[columnId]) on each cell value and checking if any includes the search term (case-insensitive). This ensures only rendered column values are matched.

Changes

• Step 1: Fix stringifyFilter to use per-column String() matching — replaced JSON.stringify(row.values) with columnIds.some() loop using String(row.values[columnId])
• Step 2: Add regression tests for false-positive search scenarios (4 new test cases covering JSON brace, column key name, ISO date milliseconds, and positive match confirmation)

Test Results

All 7 tests pass:

• ✅ it should display all the data
• ✅ it should sort by defaultSortingKey
• ✅ it should filterGlobally
• ✅ it should not produce false positive when searching for JSON brace character
• ✅ it should not produce false positive when searching for a column key name
• ✅ it should not produce false positive when searching for ISO date millisecond component
• ✅ it should still match rows when search term appears in a column value

Risks & Notes

The columnIds parameter passed by react-table v7's useGlobalFilter includes all columns where disableGlobalFilter !== true. This means columns explicitly excluded from global filtering will no longer be searchable — which is the correct behavior, unlike the previous JSON.stringify approach that searched everything indiscriminately.

References

• JIRA: RING-53752
• Tracking Issue: scality/agent-task#102

[eve-scality]

/approve

[bert-e]

Hello eve-scality,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• one peer

Peer approvals must include at least 1 approval from the following list:

• @MonPote

• @ChengYanJin

• @ZiyangLinScality

• @damiengillesscality

• @JeanMarcMilletScality

• @hervedombya

• @JBWatenbergScality

The following options are set: approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/1.0

Please check the status of the associated issue RING-53752.

Goodbye eve-scality.

The following options are set: approve