Anything with a > gets picked up as a pipe
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Review the attached screenshot and search the Ruby code for command parsing and handling of the > character. Reproduce the reported behavior, then verify that > is interpreted correctly rather than being picked up as a pipe.
Written by the indexing model from the issue text.
Description
- Dominant language
- Ruby
- Stars
- 28
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from slack-ruby/slack-shellbot
-
new feature
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
slack-ruby/slack-shellbot#24 ·
-
new feature
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
All issues in slack-ruby/slack-shellbot
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
TheOdinProject/curriculum#31408 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
notch8/utk_knapsack#148 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Homebrew/homebrew-cask#288729 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100