Skip to content
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

[Fix] Desktop timer build #8756

Merged
merged 2 commits into from
Jan 25, 2025
Merged

[Fix] Desktop timer build #8756

merged 2 commits into from
Jan 25, 2025

Conversation

adkif
Copy link
Contributor

@adkif adkif commented Jan 25, 2025

Adds constants package to desktop timer

Adds the constants package to the desktop timer application.

PR

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.


Summary by CodeRabbit

  • Chores
    • Updated project dependencies and workspace configuration
    • Added new package reference for constants

Adds constants package to desktop timer

Adds the constants package to the desktop timer application.
@adkif adkif requested a review from evereq January 25, 2025 16:49
Copy link
Contributor

coderabbitai bot commented Jan 25, 2025

Walkthrough

The pull request introduces modifications to the package.json file of the Gauzy Desktop Timer application. The changes involve adding a new workspace path for constants and including a new dependency for @gauzy/constants. This update expands the project's dependency structure and integrates a new package from the project's internal distribution.

Changes

File Change Summary
apps/desktop-timer/src/package.json - Added workspace path: ../../../dist/packages/constants
- Added dependency: "@gauzy/constants": "file:../../../dist/packages/constants"

Possibly related PRs

Suggested reviewers

  • evereq
  • rahul-rocket

Poem

🐰 A Rabbit's Workspace Ballad 🚀

New paths unfurl, dependencies dance,
Constants join our coding romance,
Workspace grows with gentle might,
Packages linking, oh so bright!
A bundle of joy, our project's delight!


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fe0a590 and 1ba1b61.

📒 Files selected for processing (1)
  • apps/desktop-timer/src/package.json (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • apps/desktop-timer/src/package.json
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: Socket Security: Pull Request Alerts
  • GitHub Check: test
  • GitHub Check: build

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@adkif adkif requested a review from rahul-rocket January 25, 2025 16:50
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e8b67d5 and fe0a590.

📒 Files selected for processing (1)
  • apps/desktop-timer/src/package.json (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: test
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: Socket Security: Pull Request Alerts
  • GitHub Check: build
🔇 Additional comments (2)
apps/desktop-timer/src/package.json (2)

28-29: LGTM! Workspace path follows existing pattern.

The addition of the constants package workspace path is consistent with other workspace entries.


28-29: Verify build configuration and dependencies

Since this PR aims to fix the desktop timer build, let's verify the package structure and build configuration.

Also applies to: 143-143

✅ Verification successful

Build paths are correct, verify build order

The paths in desktop-timer's package.json are correct:

  • Constants package builds to "dist/packages/constants"
  • The relative path "../../../dist/packages/constants" from "dist/apps/desktop-timer" is accurate

The build issue likely stems from build order rather than path configuration. Ensure the constants package is built before desktop-timer by running yarn build:package:all first.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the constants package structure and dependencies

# Check if the constants package exists in the correct location
echo "Checking for constants package..."
if [ -d "../../../dist/packages/constants" ]; then
    echo "Constants package found in workspace location"
else
    echo "Warning: Constants package not found in workspace location"
fi

# Check for any potential circular dependencies
echo "Checking for package.json in constants package..."
if [ -f "../../../dist/packages/constants/package.json" ]; then
    cat "../../../dist/packages/constants/package.json"
else
    echo "Warning: package.json not found in constants package"
fi

# Look for any other references to @gauzy/constants in the codebase
echo "Checking for other references to @gauzy/constants..."
rg -l "@gauzy/constants"

Length of output: 3784


Script:

#!/bin/bash
# Check build configuration and package structure

echo "Checking constants package.json..."
cat packages/constants/package.json

echo -e "\nChecking workspace configuration..."
cat package.json | grep -A 10 '"build":'

echo -e "\nChecking for build output configuration..."
find . -name "project.json" -exec grep -l "outputPath" {} \;

Length of output: 3572


Script:

#!/bin/bash
# Check the output path configuration for constants package

echo "Checking constants project.json for output path..."
cat packages/constants/project.json

echo -e "\nChecking desktop-timer project.json..."
cat apps/desktop-timer/project.json

Length of output: 5097

apps/desktop-timer/src/package.json Outdated Show resolved Hide resolved
Copy link

nx-cloud bot commented Jan 25, 2025

View your CI Pipeline Execution ↗ for commit 1ba1b61.

Command Status Duration Result
nx build gauzy -c=production --prod --verbose ✅ Succeeded 3m 24s View ↗
nx build api -c=production --prod ✅ Succeeded 1m 11s View ↗
nx build desktop-ui-lib --configuration=develop... ✅ Succeeded 29s View ↗
nx build plugin-integration-wakatime ✅ Succeeded <1s View ↗
nx build desktop-lib ✅ Succeeded <1s View ↗
nx build desktop-ui-lib --configuration=production ✅ Succeeded 28s View ↗
nx build desktop-window ✅ Succeeded <1s View ↗
nx build desktop-core ✅ Succeeded <1s View ↗
Additional runs (52) ✅ Succeeded ... View ↗

☁️ Nx Cloud last updated this comment at 2025-01-25 17:48:04 UTC

@evereq evereq merged commit f0e05c2 into develop Jan 25, 2025
16 of 17 checks passed
@evereq evereq deleted the fix/desktop-timer-build branch January 25, 2025 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants