Added logic to merge two function calls where the first has a name but no arguments, and the second has arguments but no name. This ensures that function calls are correctly represented when they are split across two parts.
- Updated InsightPrompts to clarify user request counting guidelines.
- Modified App.js to pass new props (topGoals, topTools) to ProjectAreas and ImpressiveWorkflows components.
- Enhanced ProjectAreas and ImpressiveWorkflows components to utilize new props for improved data visualization.
- Refactored FrictionPoints component layout to use grid display for better responsiveness.
- Removed legacy insight-app.js file to streamline the codebase.
- Expanded StaticInsightTypes to include primarySuccess, outcomes, and topGoals for better data structure.
Removes Token Usage metrics and Achievements section from the generated insight report.
- Removes calculation logic in DataProcessor
- Removes types in StaticInsightTypes
- Removes UI sections in insight-app.js
- Add HTML template for insights display.
- Create JavaScript application logic for rendering insights.
- Introduce CSS styles for layout and design.
- Develop a test generator for validating the static insight generator.
- Define TypeScript interfaces for structured insight data.
- Refactor insight command to generate insights and open in browser.
- Remove the need for a server process by generating static files directly.
- Automatically detect 'http' transport when commandOrUrl starts with http:// or https://
- Default to 'stdio' transport for non-URL commands
- Explicit --transport flag still takes precedence over auto-detection
- Update help text to indicate auto-detection capability
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Update the header info panel hint from '/auth to change' to '/model to change'
to better reflect that this command switches models rather than authentication.
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Add support for defining environment variables in settings.json files.
These variables are loaded with the lowest priority:
1. System/process environment variables (highest)
2. .env files
3. settings.env (lowest/fallback)
This allows users to configure default environment variables in their
user or workspace settings without conflicting with existing env vars
or .env file values.
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
