Repository navigation
chore: add tests for custom commands - #7357
Merged
Merged
Conversation
Nerixyz
reviewed
Oct 11, 2026
| .expected = "msg id: ", | ||
| }, | ||
| { | ||
| .command = Command("/cmd", "msg id2: {msg.id;lol xd}"), |
Contributor
There was a problem hiding this comment.
Aside: We never documented the alt text.
pajlada
approved these changes
Oct 17, 2026
pajlada
enabled auto-merge (squash)
October 17, 2026 11:49
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I wanted to add a feature to custom commands but noticed that there are no tests for the current implementation. This adds tests for custom commands and placeholder handling to ensure we(I) don't break anything in the future.