fix: add Windows path support for CursorParser and ClineParser - #25
Open
krishnesh1 wants to merge 1 commit into
Open
fix: add Windows path support for CursorParser and ClineParser#25krishnesh1 wants to merge 1 commit into
krishnesh1 wants to merge 1 commit into
Conversation
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed?
Added Windows path support for
CursorParserandClineParser.- Imported the
osmodule in both parser files.- Used
os.getenv("APPDATA")with a fallback to~/AppData/Roamingto locate the%APPDATA%directorydynamically on Windows machines.
- Added
windows_pathconfiguration strings matching the target application data stores for both Cursor andCline.
- Incorporated the
windows_pathdirectory check into the main parser__init__resolution chains.discover log paths (
~/.configand~/Library/Application Support/). This caused the tool to silently fail andreport zero telemetry on Windows.
suite checks for missing directories continue to pass as expected.
purely additive and does not modify the telemetry parsing logic itself, so it shouldn't disrupt existing telemetry
capabilities on non-Windows environments.