Skip to content

Conversation

@scopsy
Copy link
Contributor

@scopsy scopsy commented Apr 24, 2025

What changed? Why was the change needed?

Screenshots

Expand for optional sections

Related enterprise PR

Special notes for your reviewer

organizationId: user.organizationId,
userId: user._id,
topicKey,
force: true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's fix this one, we are telling the users in the exception that they can pass force=true while it is not possible.

Suggested change
force: true,
force: query.force || false,

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We actually don't tell this to users, I have kept it as only internal thing. Where di you see it?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed this in the DeleteTopicUseCase. Just sharing a few thoughts, no need to answer directly:
If we don’t plan to expose this route externally, do we really need this logic?
If or when we do expose it, we should make sure to revisit and update this part accordingly.

@scopsy scopsy merged commit 2d22010 into next May 8, 2025
29 of 30 checks passed
@scopsy scopsy deleted the topics-page branch May 8, 2025 20:22
bricehemery pushed a commit to jack-agency/novu that referenced this pull request Jul 7, 2025
Co-authored-by: George Djabarov <39195835+djabarovgeorge@users.noreply.github.com>
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.

3 participants