skyra-project / tags Goto Github PK

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency @sapphire/eslint-config to v5
• chore(deps): update dependency @sapphire/prettier-config to v2
• chore(deps): update dependency eslint-plugin-prettier to v5
• chore(deps): update typescript-eslint monorepo to v6 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Click on this checkbox to rebase all open PRs at once

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update dependency prettier to v3

Detected dependencies

npm

package.json

• tslib ^2.6.0
• @commitlint/cli ^17.6.7
• @commitlint/config-conventional ^17.6.7
• @sapphire/eslint-config ^4.4.3
• @sapphire/prettier-config ^1.4.5
• @sapphire/ts-config ^4.0.1
• @types/node ^18.17.0
• @typescript-eslint/eslint-plugin ^5.62.0
• @typescript-eslint/parser ^5.62.0
• @vitest/coverage-v8 ^0.33.0
• cz-conventional-changelog ^3.3.0
• eslint ^8.45.0
• eslint-config-prettier ^8.8.0
• eslint-plugin-prettier ^4.2.1
• gen-esm-wrapper ^1.1.3
• husky ^8.0.3
• lint-staged ^13.2.3
• prettier ^2.8.8
• pretty-quick ^3.1.3
• standard-version ^9.5.0
• typedoc ^0.24.8
• typescript ^5.1.6
• vitest ^0.33.0
• ansi-regex ^5.0.1
• minimist ^1.2.8
• yarn 3.6.1

---

• Check this box to trigger a request for Renovate to run again on this repository

Is your feature request related to a problem? Please describe.

Sometimes, admins may want to customize the error message Skyra sends, for example, in a slap command, the admin may want Skyra to send Who do you want to slap? when the argument fails to be resolved, instead of the generic You must provide a valid user.

Describe the solution you'd like

We can use #{str} inside tags, e.g:

{author} gave {user #{Who do you want to slap?}} a big slap! {random {url1} {url2} {url3} {url4}} (complementing #1).

Error messages are not affected by transformations - because they're not part of the output message, but an error.

It can also be weird if somebody did Echo: {string... #{Please specify the content} | bold | uppercase}, the admin expects this to return Echo: **SUCH WOW** when somebody runs it with s!mycommand such wow, but it's hardly expectable in the error itself - which would show **PLEASE SPECIFY THE CONTENT** if it did.

Describe alternatives you've considered

N/a.

Additional context

N/a.

Is your feature request related to a problem? Please describe.

Sometimes, the user may want Skyra to reply with a random message, e.g. one of a collection of urls.

Describe the solution you'd like

{random {url1} {url2} {url3}}

Transformers would also be supported:

What is the best? {random {google} {bing} {ddg} | bold} outputs one of What is best? **google**, What is best? **bing**, and What is best? **ddg**.

The validation is that random tags must have at least one option. Throwing an error when none was provided.

Describe alternatives you've considered

N/a.

Additional context

N/a.