- Extract message response logic into a new method shouldSendResponse
- Remove redundant try/catch blocks for parsing message text
- Improve readability and maintainability of the handleMessage method
- Comment out refDefsContext and defRefsContext usage in loadContexts
- Replace accessKey logic with defaultModel in several files
- Remove unused functions related to API key handling
Closes#286
- Added feature toggles for beta commands in the package.json file.
- Implemented dynamic registration of commands based on feature toggles.
- Added error messages for users trying to access beta commands without the correct permissions.
- Updated the version of the devchat-ask package based on the feature toggles.
- Created a new featureToggle handler to manage feature toggles.
- Added new settings for Python virtual environment and supported file types in package.json.
- Added new commands for starting and stopping AskCode Index in package.json.
- Registered new 'ask-code' command in CommandManager.
- Registered AskCode Index start and stop commands in extension.ts.
- Added 'askCode' handler in loadHandlers.ts and messageHandler.ts.
- Updated messageHandler to check for '/ask-code' in message text and call 'askCode' command.
- Refactored applyAction to include parentHash in the message.
- Simplified codeFileApply function by removing redundant error handling.
- Enhanced error handling in MessageHandler to include parentHash.
- Added condition to regenerate message only if autox is true.
- Added a global variable 'autox' to control automatic execution of commands.
- Updated the 'sendMessage' function to handle '/autox' in the message text.
- If 'autox' is true and the message contains a command, the command is automatically executed.
- This feature will help in automating tasks and improving efficiency.
- Implement Topic and TopicManager classes.
- Add TopicTreeDataProvider and TopicTreeItem classes.
- Register new commands for topic management.
- Update package.json with new commands and dependencies.
This commit enhances the handling of missing or invalid OPENAI_API_KEY
by adding validation checks and providing clear error messages to the
user. It also stores the valid API key in the secret storage and
displays a welcome message when the key is set correctly.