Problem
Currently, the extension generates logs by attempting to guess the active project based on file names and file structure. This approach can be unreliable, especially in multi-project repositories or when file naming conventions are inconsistent. As a result, logs may be incorrectly attributed or lack necessary project-specific context.
Proposed Solution
- Implement a mechanism to accurately detect and track which project the user is actively working on.
- Ensure that all generated logs explicitly reference the detected project context.
- Explore options such as workspace configuration, project metadata, or integration with IDE APIs to enhance contextual awareness.
- Update the log generation logic to use this new context-aware approach.
Acceptance Criteria
- Logs are consistently and accurately associated with the project the user is working on.
- The solution works for mono-repos, multi-project workspaces, and nested directory structures.
- Documentation is updated to explain how project context is determined and used in log generation.
This feature will improve the reliability and usefulness of logs generated by the extension, helping users better track and analyze their activity.
Problem
Currently, the extension generates logs by attempting to guess the active project based on file names and file structure. This approach can be unreliable, especially in multi-project repositories or when file naming conventions are inconsistent. As a result, logs may be incorrectly attributed or lack necessary project-specific context.
Proposed Solution
Acceptance Criteria
This feature will improve the reliability and usefulness of logs generated by the extension, helping users better track and analyze their activity.