Raku / Raku/whateverable

Don't print the nickname if not needed

Open
#265 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

all bots evalable whateverable
Dominant language
Raku
Stars
19
Forks
16
PR merge metrics
No merged PRs in 30d

Description

<AlexDaniel> m: say 42; say 43
<camelia> rakudo-moar 4a32089fd: OUTPUT: «42␤43␤»
<AlexDaniel> eval: say 42; say 43
<evalable6> AlexDaniel, rakudo-moar 4a32089fd: OUTPUT: «42␤43␤»

Looking at this, maybe starting the message with “AlexDaniel,” is a little bit redundant. There are cases when more than one person address the bot simultaneously, and in these cases indeed the nickname should be printed. But otherwise I think it's safe to omit it. Would be great if it was able to adjust to the situation accordingly.

Contributor guide

Open the contributing guide

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.

Research direction

The issue names no files or tests; start by tracing how the bot handles the m and eval examples and assembles replies. Define done as omitting the nickname for a single addressed request while retaining it when multiple people address the bot, and verify both cases.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.