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 example build script #3116

Merged
merged 1 commit into from
Feb 17, 2025
Merged

Fix example build script #3116

merged 1 commit into from
Feb 17, 2025

Conversation

Mrtenz
Copy link
Member

@Mrtenz Mrtenz commented Feb 17, 2025

The build script for examples broke in #3094. Using the filter command seems to be the easiest way to get it working again.

@Mrtenz Mrtenz requested a review from a team as a code owner February 17, 2025 15:48
Copy link

codecov bot commented Feb 17, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.88%. Comparing base (7c26c26) to head (74b9bc0).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3116   +/-   ##
=======================================
  Coverage   94.88%   94.88%           
=======================================
  Files         506      506           
  Lines       11121    11121           
  Branches     1709     1709           
=======================================
  Hits        10552    10552           
  Misses        569      569           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -20,7 +20,7 @@
"sideEffects": false,
"files": [],
"scripts": {
"build": "yarn workspaces foreach --worktree --parallel --verbose --no-private run build",
"build": "yarn workspaces filter --include 'packages/examples/packages/**' --parallel --no-private run build",
Copy link
Contributor

@hmalik88 hmalik88 Feb 17, 2025

Choose a reason for hiding this comment

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

What's the difference between doing yarn workspaces filter --include and yarn workspaces foreach --include? Why don't we need --verbose any more?

Copy link
Member

Choose a reason for hiding this comment

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

--verbose doesn't exist on filter

Copy link
Member Author

Choose a reason for hiding this comment

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

workspaces filter's --include supports glob patterns, whereas workspaces foreach only supports exact package names. --verbose is also enabled by default on workspaces filter.

@Mrtenz Mrtenz force-pushed the mrtenz/example-build-script branch from 0eaa757 to 74b9bc0 Compare February 17, 2025 16:34
@Mrtenz Mrtenz merged commit f17d19d into main Feb 17, 2025
169 checks passed
@Mrtenz Mrtenz deleted the mrtenz/example-build-script branch February 17, 2025 16:43
Mrtenz added a commit to Mrtenz/snaps that referenced this pull request Mar 13, 2025
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.

3 participants