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

Refresh list after "delete 50 files" #21

Open
alexbayleaf opened this issue Dec 1, 2021 · 2 comments
Open

Refresh list after "delete 50 files" #21

alexbayleaf opened this issue Dec 1, 2021 · 2 comments

Comments

@alexbayleaf
Copy link

What happens:

  1. I filter and get a large result set, say 200 files
  2. I click "DELETE 50 FILES" to delete the first 50
  3. The result set (main area of screen) is now blank
  4. I re-apply the filter to see the remaining 150 files

What I'd like to happen: at point 3, the result set automatically shows the remaining 150 files, allowing me to delete the next 50 with one click.

@drewminns
Copy link
Owner

Hey there. Stoked you're using it. A lot of the UX is the result of what Slack allows to users to do with their API. That includes rate limiting requests and only providing certain information.

I recommend giving the api and codebase a quick look to understand why the decisions were made. Or better yet, poke Slack and tell them to make more info available for devs! https://api.slack.com/methods :)

@alexbayleaf
Copy link
Author

Hmmm so you're on Web API Tier 1 I presume (free?) ... and re-sending the request automatically would make it too easy for someone to just pound on the "delete 50" button and exceed the rate limit. Got it.

Might be a bit fiddly, but I'm wondering whether it'd be possible to, like, do a wait(60) (yes I know JS doesn't have wait function, you know what I mean) with a spinning icon and maybe a message like "Refreshing list in N seconds to obey Slack's rate limits" ... at least saving the user from having to re-do the filter and letting them know why it is the way it is.

I mean this is heading deep into "it would be nice if..." land, at least if I know the reason is APi rate limiting I can shrug and deal with it ;)

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

No branches or pull requests

2 participants