From bdc797d5c107136a1e7afec0244fcf2b109b2c0d Mon Sep 17 00:00:00 2001 From: "Felipe M." Date: Mon, 23 Jun 2025 11:34:27 +0200 Subject: [PATCH 1/2] chore: make format --- internal/platform/telegram/telegram.go | 2 +- internal/plugin/social/twitter_test.go | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/internal/platform/telegram/telegram.go b/internal/platform/telegram/telegram.go index 07c65a9..d35bb6b 100644 --- a/internal/platform/telegram/telegram.go +++ b/internal/platform/telegram/telegram.go @@ -236,7 +236,7 @@ func (t *TelegramPlatform) SendMessage(msg *model.Message) error { "chat_id": chatID, "text": msg.Text, } - + // Set parse_mode based on plugin preference or default to Markdown if msg.Raw != nil && msg.Raw["parse_mode"] != nil { // Plugin explicitly set parse_mode diff --git a/internal/plugin/social/twitter_test.go b/internal/plugin/social/twitter_test.go index d94cad4..c0e1681 100644 --- a/internal/plugin/social/twitter_test.go +++ b/internal/plugin/social/twitter_test.go @@ -117,4 +117,4 @@ func TestTwitterExpander_OnMessage(t *testing.T) { } }) } -} \ No newline at end of file +} From 3a5b5c216ddc3c719c095bbf7bf40d80e344b391 Mon Sep 17 00:00:00 2001 From: "Felipe M." Date: Mon, 23 Jun 2025 11:35:30 +0200 Subject: [PATCH 2/2] chore: try to ensure that code is checked after each session --- CLAUDE.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 0261dd2..cb4e70a 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -18,10 +18,12 @@ When creating, modifying, or removing plugins: ## Testing -After every session that contains changes to files: +**CRITICAL**: After making ANY changes to code files, you MUST run these commands in order: -1. Check files are properly formatted running `make format` -2. Check code style and linting: Run `make lint` -3. Test the plugin functionality: Run `make test` +1. **Format code**: `make format` - Format all code according to project standards +2. **Lint code**: `make lint` - Check code style and quality (must show "0 issues") +3. **Run tests**: `make test` - Run all tests to ensure functionality works 4. Verify documentation accuracy 5. Ensure all examples work as described + +**These commands are MANDATORY after every code change, no exceptions.**