Claude e8b99d99b8 Fix validation error: make newApplications field optional in OrganizationReportSummary ...

The validation functions required the newApplications field to be present,
but this field is not in the type definition and old encrypted data doesn't
have it. This was causing decryption failures with the error:
"Invalid OrganizationReportSummary: missing or invalid fields: newApplications (string[])"

Changes:
- Updated isOrganizationReportSummary() to allow newApplications to be undefined
- Updated validateOrganizationReportSummary() to only validate newApplications if present
- Added comments explaining backward compatibility requirement

This provides backward compatibility with existing encrypted data while still
validating the field when it is present.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-10-30 04:42:15 +00:00

..

src

Fix validation error: make newApplications field optional in OrganizationReportSummary

2025-10-30 04:42:15 +00:00

jest.config.js

Implement and extend tsconfig.base across projects (#14554)

2025-06-02 20:38:17 +00:00

test.setup.ts

[PM-18599] Forbid unknown property and element in tests (#13556)

2025-02-25 14:02:19 -08:00

tsconfig.json

Implement and extend tsconfig.base across projects (#14554)

2025-06-02 20:38:17 +00:00

tsconfig.spec.json

[AC-2302] Extract device approve/deny logic into a service (#8818)

2024-05-20 11:18:23 +01:00