Refactor for BotPlatform update and Telegram class usage #153
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.
This PR refactors the ScriptureBot to align with the latest changes in BotPlatform (PR #17).
Key changes:
TELEGRAM_ADMIN_IDis now handled inSecretsData.Telegramclass is now instantiated with secrets (TELEGRAM_ID,TELEGRAM_ADMIN_ID) instead of relying on global state orenv.Secrets.platform.PostFromPropscalls withbot.Post(env)method calls.platform.Platforminterface throughProcessCommand,RunCommands,HandleBotLogic, andGetDevo.env.Secretsusage (as it was removed fromSessionData) and replaced it with direct calls tosecrets.Get()forPROJECT_IDandADMIN_ID.MockBotfor unit testing the app logic without a real bot instance. Updated integration tests.PR created automatically by Jules for task 5141351822751200936 started by @julwrites