Blocking of several users ends prematurely if t comes across a nonexistent/suspended user

Open
#199 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
cli

Research direction

Start by tracing the block command's handling of multiple usernames, using the example with User1, NonexistentUser, and User2. Run that case with a nonexistent or suspended account; done means later valid users are still processed and the skipped user receives a friendly message.

Written by the indexing model from the issue text.

Description

bug

When blocking multiple users at once (e.g. cat-ing a list and using xargs), t will fail to block any users listed after a nonexistent or suspended user.

For example:
t block User1 NonexistentUser User2

In this case, t will block User1 but will return a Sorry, that page does not exist error for NonexistentUser and exit. User2 will not be blocked.

It would be good if t handled this issue gracefully, preferably with a user friendly message (e.g. "Skipping user .")

Dominant language
Ruby
Stars
5.6k
Forks
402
Avg merge
13h 50m
Merged PRs (30d)
5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sferik/x-cli

All issues in sferik/x-cli

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.