fix: Trim whitespace in is_admin_command #1836

Merged
ginger merged 1 commit from kitvonsnookerz/continuwuity:fix/1804-leading-whitespace into main 2026-06-11 15:20:35 +00:00
Contributor

This pull request trims whitespace from is_admin_command, which lets users run commands even with a space before the !admin prefix.

Pull request checklist:

  • This pull request targets the main branch, and the branch is named something other than
    main.
  • I have written an appropriate pull request title and my description is clear.
  • I understand I am responsible for the contents of this pull request.
  • I have followed the contributing guidelines:
<!-- In order to help reviewers know what your pull request does at a glance, you should ensure that 1. Your PR title is a short, single sentence describing what you changed 2. You have described in more detail what you have changed, why you have changed it, what the intended effect is, and why you think this will be beneficial to the project. If you have made any potentially strange/questionable design choices, but didn't feel they'd benefit from code comments, please don't mention them here - after opening your pull request, go to "files changed", and click on the "+" symbol in the line number gutter, and attach comments to the lines that you think would benefit from some clarification. --> This pull request trims whitespace from `is_admin_command`, which lets users run commands even with a space before the !admin prefix. <!-- Example: This pull request allows us to warp through time and space ten times faster than before by double-inverting the warp drive with hyperheated jump fluid, both making the drive faster and more efficient. This resolves the common issue where we have to wait more than 10 milliseconds to engage, use, and disengage the warp drive when travelling between galaxies. --> <!-- Closes: #... --> <!-- Fixes: #... --> <!-- Uncomment the above line(s) if your pull request fixes an issue or closes another pull request by superseding it. Replace `#...` with the issue/pr number, such as `#123`. --> **Pull request checklist:** <!-- You need to complete these before your PR can be considered. If you aren't sure about some, feel free to ask for clarification in #dev:continuwuity.org. --> - [x] This pull request targets the `main` branch, and the branch is named something other than `main`. - [x] I have written an appropriate pull request title and my description is clear. - [x] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [x] My contribution follows the [code style][c2], if applicable. - [x] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [x] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [x] My commit messages follow the [commit message format][c1cm] and are descriptive. <!-- Notes on these requirements: - While not required, we encourage you to sign your commits with GPG or SSH to attest the authenticity of your changes. - While we allow LLM-assisted contributions, we do not appreciate contributions that are low quality, which is typical of machine-generated contributions that have not had a lot of love and care from a human. Please do not open a PR if all you have done is asked ChatGPT to tidy up the codebase with a +-100,000 diff. - In the case of code style violations, reviewers may leave review comments/change requests indicating what the ideal change would look like. For example, a reviewer may suggest you lower a log level, or use `match` instead of `if/else` etc. - In the case of code style violations, pre-commit check failures, minor things like typos/spelling errors, and in some cases commit format violations, reviewers may modify your branch directly, typically by making changes and adding a commit. Particularly in the latter case, a reviewer may rebase your commits to squash "spammy" ones (like "fix", "fix", "actually fix"), and reword commit messages that don't satisfy the format. - Pull requests MUST pass the `Checks` CI workflows to be capable of being merged. This can only be bypassed in exceptional circumstances. If your CI flakes, let us know in matrix:r/dev:continuwuity.org. - Pull requests have to be based on the latest `main` commit before being merged. If the main branch changes while you're making your changes, you should make sure you rebase on main before opening a PR. Your branch will be rebased on main before it is merged if it has fallen behind. - We typically only do fast-forward merges, so your entire commit log will be included. Once in main, it's difficult to get out cleanly, so put on your best dress, smile for the cameras! --> [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages
Issue #1804 trimmed whitespace on possible command
Some checks failed
Auto Labeler / Apply labels based on changed files (pull_request_target) Successful in 4s
Checks / Changelog / Check changelog is added (pull_request_target) Failing after 10s
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Checks / Prek / Check changed files (pull_request) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
d98f804305
ignore this silly mistake
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Failing after 7s
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Checks / Prek / Check changed files (pull_request) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
a31be06aa1
added a change log
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Check changed files (pull_request) Successful in 4s
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 1m26s
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
48ab4f8ef3
Henry-Hiles requested changes 2026-06-08 18:29:08 +00:00
Dismissed
@ -549,14 +549,16 @@ impl Service {
return None;
}
let trimmed_body: &str = body.trim_start();
Member

Should this not be inside the if let?

Should this not be inside the `if let`?
Member

Nevermind.

Nevermind.
Henry-Hiles marked this conversation as resolved
@ -554,3 +555,4 @@
{
// This is a message in the admin room
// spaces are allowed
Member

I'd replace this with a comment next to trimmed_body, saying something like // Trim leading spaces from commands

I'd replace this with a comment next to `trimmed_body`, saying something like `// Trim leading spaces from commands`
kitvonsnookerz marked this conversation as resolved
kitvonsnookerz force-pushed fix/1804-leading-whitespace from 48ab4f8ef3
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Check changed files (pull_request) Successful in 4s
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 1m26s
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
to 1dc7b502e6
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Check changed files (pull_request) Successful in 7s
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 59s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 8m50s
2026-06-08 18:29:58 +00:00
Compare
Member

The commit message should probably say "Trim whitespace" not "Trimmed whitespace", should give extra information on another line, and shouldn't end in a period.

For example, instead of the current message:

fix: Trimmed whitespace in is_admin_command to allow users to send commands if they accidently put a space in front of admin commands.

You could have:

fix: Trim whitespace in is_admin_command

This allows users to send commands if they accidentally put a space in front of admin commands.

EDIT: This has been resolved.

The commit message should probably say "Trim whitespace" not "Trimmed whitespace", should give extra information on another line, and shouldn't end in a period. For example, instead of the current message: ``` fix: Trimmed whitespace in is_admin_command to allow users to send commands if they accidently put a space in front of admin commands. ``` You could have: ``` fix: Trim whitespace in is_admin_command This allows users to send commands if they accidentally put a space in front of admin commands. ``` EDIT: This has been resolved.
Henry-Hiles changed title from Issue #1804 trimmed whitespace on possible command to fix: Trim whitespace in is_admin_command 2026-06-08 18:32:13 +00:00
kitvonsnookerz force-pushed fix/1804-leading-whitespace from 1dc7b502e6
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Check changed files (pull_request) Successful in 7s
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 59s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 8m50s
to ea4034eb74
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Update flake hashes / update-flake-hashes (pull_request) Failing after 2m0s
Checks / Prek / Check changed files (pull_request) Failing after 2m0s
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been skipped
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 6m25s
2026-06-08 20:35:15 +00:00
Compare
Merge branch 'main' into fix/1804-leading-whitespace
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Checks / Prek / Check changed files (pull_request) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
5c5d1d9b54
kitvonsnookerz force-pushed fix/1804-leading-whitespace from 5c5d1d9b54
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Checks / Prek / Check changed files (pull_request) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
to ea4034eb74
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Update flake hashes / update-flake-hashes (pull_request) Failing after 2m0s
Checks / Prek / Check changed files (pull_request) Failing after 2m0s
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been skipped
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 6m25s
2026-06-08 21:03:24 +00:00
Compare
Henry-Hiles left a comment

LGTM with my very limited rust knowledge.

LGTM with my very limited rust knowledge.
ginger approved these changes 2026-06-09 14:27:31 +00:00
ginger scheduled this pull request to auto merge when all checks succeed 2026-06-09 14:27:37 +00:00
ginger merged commit 0ece17b6a0 into main 2026-06-11 15:20:35 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
continuwuation/continuwuity!1836
No description provided.