ENG-1796 - /aggregate-results returns confidence scores as optional

[vcruces]

Ticket ENG-1796

Description Of Changes

This PR updates the frontend to handle optional confidence score fields in datastore monitor updates and removes the classified_manually field that is no longer needed.

⚠️ These changes align with backend updates in fidesplus branch ENG-1796-confidence-score.

The classified_low_confidence and classified_high_confidence fields are now optional and nullable, as they may not always be present in monitor update responses. The classified_manually classification type has been removed from the system.

Code Changes

• Updated DatastoreMonitorUpdates TypeScript type to make classified_low_confidence and classified_high_confidence optional and nullable
• Removed classified_manually field from the monitor updates type definition
• Added null check in MonitorResultDescription.tsx to handle nullable count values before filtering
• Removed classified_manually from the MONITOR_UPDATES_TO_IGNORE constants array
• Updated test fixture aggregate-results.json to remove the classified_manually field

Steps to Confirm

1. Run the admin UI and navigate to the action center (enable the alpha flag)
2. Verify that monitor results display correctly without errors
3. Verify that the UI handles missing confidence score fields gracefully

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• UX feedback:
  • All UX related changes have been reviewed by a designer
  • No UX review needed
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
fides-plus-nightly	Ready	Preview	Comment	Oct 29, 2025 6:39pm

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
fides-privacy-center	Ignored			Oct 29, 2025 6:39pm

[greptile-apps]

Greptile Overview

Greptile Summary

This PR updates the frontend to handle optional confidence score fields (classified_low_confidence and classified_high_confidence) in datastore monitor updates, aligning with backend API changes. The classified_manually field has been removed from the type definition, constants, and test fixtures.

Key changes:

• Type definition updated to make confidence fields optional and nullable
• Added proper null checking in MonitorResultDescription.tsx before filtering and formatting
• Removed classified_manually from ignored fields array
• Updated test fixture to match new type structure

The implementation correctly handles the nullable fields by filtering out null/undefined values before processing, and uses a non-null assertion operator after the filter, which is safe since the filter ensures only non-null values pass through.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The changes are straightforward type updates with proper null handling. The null check is correctly placed in the filter before any value usage, and the non-null assertion is safe after filtering. All references to the removed field have been cleaned up, and test fixtures have been updated accordingly.
• No files require special attention

Important Files Changed

File Analysis

Filename	Score	Overview
clients/admin-ui/src/types/api/models/DatastoreMonitorUpdates.ts	5/5	Made confidence fields optional/nullable and removed classified_manually field - aligns with backend API changes
clients/admin-ui/src/features/data-discovery-and-detection/action-center/MonitorResultDescription.tsx	5/5	Added null check in filter to handle optional confidence fields - correctly uses non-null assertion after filtering

_{4 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}