Skip to content

Conversation

@scopsy
Copy link
Contributor

@scopsy scopsy commented Nov 25, 2025

What changed? Why was the change needed?

Screenshots

Expand for optional sections

Related enterprise PR

Special notes for your reviewer

Updated the type of the subscriber variable in update and get preference use cases to Pick<SubscriberEntity, '_id'> for improved type safety and clarity. Adjusted repository method call to only fetch the '_id' field where applicable.
Switched from a local deepMerge utility to the deepmerge-ts package for merging preferences in the upsert-preferences usecase. Added deepmerge-ts as a dependency in package.json to improve maintainability and reliability.
@netlify
Copy link

netlify bot commented Nov 25, 2025

Deploy Preview for dashboard-v2-novu-staging canceled.

Name Link
🔨 Latest commit 9dd582c
🔍 Latest deploy log https://app.netlify.com/projects/dashboard-v2-novu-staging/deploys/6926c2fe34935b00088a36da

@github-actions
Copy link
Contributor

github-actions bot commented Nov 25, 2025

Hey there and thank you for opening this pull request! 👋

We require pull request titles to follow specific formatting rules and it looks like your proposed title needs to be adjusted.

Your PR title is: refactor(api-service): deep merge ts migration

Requirements:

  1. Follow the Conventional Commits specification
  2. As a team member, include Linear ticket ID at the end: fixes TICKET-ID or include it in your branch name

Expected format: feat(scope): Add fancy new feature fixes NOV-123

Details:

PR title must end with 'fixes TICKET-ID' (e.g., 'fixes NOV-123') or include ticket ID in branch name

@scopsy scopsy changed the title fix: deep merge test refactor(api-service): deep merge test Nov 25, 2025
@scopsy scopsy changed the title refactor(api-service): deep merge test refactor(api-service): deep merge ts migration Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants