Skip to content

Conversation

@NevilleS
Copy link
Contributor

@NevilleS NevilleS commented Dec 9, 2025

Ticket []

Description Of Changes

Code Changes

Steps to Confirm

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

…attern

- Refactor makeDefaultIdentity to accept options object with fidesUserDeviceId and fidesExternalId
- Update getOrMakeFidesCookie and makeFidesCookie to use Pick<FidesInitOptions, ...> for type safety
- Move fidesExternalId to options object alongside fidesClearCookie and fidesCookieSuffix
- Add comprehensive test coverage for makeDefaultIdentity
- Update all call sites to use new function signatures
- Streamline and remove duplicate tests
- Fix identity merging to handle undefined parsedCookie.identity gracefully
Update validation regex from /(.*)/ to /.+/ to explicitly reject empty strings.
This makes the validation more explicit and self-documenting, requiring
at least one character for the external ID.
- Remove redundant branch for handling missing device ID
- Streamline logic to handle undefined identity first, then update external_id
- Add test coverage for undefined identity with and without fidesExternalId
@vercel
Copy link

vercel bot commented Dec 9, 2025

Deployment failed with the following error:

You must set up Two-Factor Authentication before accessing this team.

View Documentation: https://vercel.com/docs/two-factor-authentication

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants