Skip to content
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

Bulk destroy notifications #172

Open
Mack241 opened this issue Sep 20, 2023 · 2 comments
Open

Bulk destroy notifications #172

Mack241 opened this issue Sep 20, 2023 · 2 comments
Labels
need more info We need more information

Comments

@Mack241
Copy link

Mack241 commented Sep 20, 2023

Problem or use case:

Couldn't find a way to delete more than one notification for a target. While the destroy API provides functionality to destroy a single notification, I don't see a way to destroy more than one.

Expected solution

Availability of a bulk_destroy API

Alternatives

Provision to create custom APIs which can be leveraged to bulk destroy notifications

@simukappu
Copy link
Owner

You can build your own bulk destroy API by directly deleting notification model or records on DB.
If we need to prepare common bulk destroy API, what kind of filter conditions for specifying target notifications to destroy do you want?

@simukappu simukappu added the need more info We need more information label Oct 20, 2023
@Mack241
Copy link
Author

Mack241 commented Oct 27, 2023

Maybe I wasn't clear earlier. When I meant an API for bulk_destroy, I meant a "route". Currently there is no provision to add a new route to my NotificationsController. Because I believe we can only work with routes like index, open_all, show, open, destroy and move

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need more info We need more information
Projects
None yet
Development

No branches or pull requests

2 participants