-
Notifications
You must be signed in to change notification settings - Fork 0
Refactor codebase toward domain-driven design patterns #116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…gration Co-authored-by: tacosontitan <65432314+tacosontitan@users.noreply.github.com>
Co-authored-by: tacosontitan <65432314+tacosontitan@users.noreply.github.com>
Co-authored-by: tacosontitan <65432314+tacosontitan@users.noreply.github.com>
Co-authored-by: tacosontitan <65432314+tacosontitan@users.noreply.github.com>
…ands Co-authored-by: tacosontitan <65432314+tacosontitan@users.noreply.github.com>
Co-authored-by: tacosontitan <65432314+tacosontitan@users.noreply.github.com>
…nd word of the day Co-authored-by: tacosontitan <65432314+tacosontitan@users.noreply.github.com>
- Add cycle time calculation for completed bugs and user stories - Display average cycle time in Overview view as separate tile - Asynchronously loads cycle time data to avoid blocking UI - Shows loading state while fetching data - Handles errors gracefully without disrupting main greeting - Filters to only bugs and user stories as requested - Calculates time from activated to closed state Co-authored-by: tacosontitan <65432314+tacosontitan@users.noreply.github.com>
Co-authored-by: tacosontitan <65432314+tacosontitan@users.noreply.github.com>
Co-authored-by: tacosontitan <65432314+tacosontitan@users.noreply.github.com>
Co-authored-by: tacosontitan <65432314+tacosontitan@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR refactors the codebase toward domain-driven design patterns by introducing a comprehensive time tracking feature and reorganizing the extension structure. The primary changes include implementing a complete time tracking system with data retention policies, adding meeting notes functionality, and establishing better separation of concerns through modular architecture.
- Complete time tracking system with clock in/out functionality, data persistence, and automatic cleanup
- Meeting notes functionality with customizable templates and Azure DevOps integration
- Enhanced overview webview with work item analytics and personalized dashboard
- Improved command registry architecture with better dependency injection and service separation
Reviewed Changes
Copilot reviewed 17 out of 17 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| src/extension/time/* | New time tracking domain with services, data models, tree providers, and commands |
| src/extension/meetings/* | New meeting notes domain with templates, participant configuration, and webview integration |
| src/extension/overview/overview-webview-provider.ts | Enhanced overview with DevOps analytics and improved UI |
| src/extension/test/* | Comprehensive test coverage for time tracking and data retention functionality |
| src/extension/core/command-registry.ts | Refactored command registration with improved dependency management |
| package.json | Updated configuration schema and command definitions for new features |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
The primary objective of this PR is to refactor the entire codebase toward domain-driven design patterns. This extension has potential to grow its feature set without limitation which means maintenance should be simple and expansion should require minimal effort to keep units of work small and focused. While there will be a lot of changes with this PR, they are all changes I believe to be beneficial to the ideas and goals I have in mind for the project.