-
Notifications
You must be signed in to change notification settings - Fork 4.2k
feat(api, dashboard): Topics management #8193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| organizationId: user.organizationId, | ||
| userId: user._id, | ||
| topicKey, | ||
| force: true, |
There was a problem hiding this comment.
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.
| force: true, | |
| force: query.force || false, |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
Co-authored-by: George Djabarov <39195835+djabarovgeorge@users.noreply.github.com>
What changed? Why was the change needed?
Screenshots
Expand for optional sections
Related enterprise PR
Special notes for your reviewer