fix: data sync optimization

[Friedrich482]

Commits

• fix: data sync optimization

  • removed the projectPath and branchName fields from the attributes of individual files in the todayFilesData object sent to the server because those are already taken in account in the shape of the object
  • this fixes the issue of the data comparison between todayFilesData about to be sent and the global state data, which was always failing because of those additional fields
  • bumped the extension version to v0.0.71

Summary by CodeRabbit

• Bug Fixes

  • Improved synchronization data handling by removing unnecessary project path and branch details from stored daily file activity.

• Chores

  • Updated the VS Code extension version to 0.0.71.

[coderabbitai]

Warning

Review limit reached

@Friedrich482, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 55624fdf-ba4d-4106-bc6d-35af7cee8f3e

📥 Commits

Reviewing files that changed from the base of the PR and between c9fdd62 and d481703.

📒 Files selected for processing (2)

• .github/workflows/publish-extension.yaml
• apps/vscode-extension/package.json

📝 Walkthrough

Walkthrough

The VS Code extension’s per-file periodic sync data no longer stores projectPath or branchName, and the published extension version is incremented from 0.0.70 to 0.0.71.

Changes

VS Code extension update

Layer / File(s)	Summary
Per-file sync payload apps/vscode-extension/src/utils/periodic-sync-data.ts	Per-file sync objects now retain timeSpent, fileName, languageSlug, and projectName without projectPath or branchName.
Extension release version apps/vscode-extension/package.json	The published extension version changes from 0.0.70 to 0.0.71.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• Friedrich482/mooncode#131: Also changes the per-file todayFilesData sync payload in the VS Code extension.
• Friedrich482/mooncode#138: Also updates only the VS Code extension manifest version.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is relevant to the main change, describing a data sync optimization that matches the payload cleanup and version bump.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch branching

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/vscode-extension/package.json`:
- Line 5: Keep the extension manifest version at 0.0.70 in package.json, since
publish:patch already increments it before publishing; do not commit the
pre-bumped 0.0.71 value unless the workflow is changed to use vsce publish.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ca98e7d4-f018-4840-bec1-3b4d62d20874

📥 Commits

Reviewing files that changed from the base of the PR and between b950ca5 and c9fdd62.

📒 Files selected for processing (2)

• apps/vscode-extension/package.json
• apps/vscode-extension/src/utils/periodic-sync-data.ts

💤 Files with no reviewable changes (1)

• apps/vscode-extension/src/utils/periodic-sync-data.ts