Skip to content

Fix test environment public_path for webpacker#8953

Merged
machida merged 5 commits intomainfrom
image-path-css
Jul 18, 2025
Merged

Fix test environment public_path for webpacker#8953
machida merged 5 commits intomainfrom
image-path-css

Conversation

@machida
Copy link
Copy Markdown
Member

@machida machida commented Jul 18, 2025

Summary by CodeRabbit

  • 修正
    • テスト環境のパック公開パスを本番環境と同じ /packs/ に統一しました。
    • Sassの画像URL解決をWebpackのエイリアスから固定の相対パスに変更し、Railsのアセットホストでの画像配信に対応しました。

Add public_path setting for test environment to prevent CI failures
caused by incorrect asset paths in test environment.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Jul 18, 2025

Walkthrough

config/webpacker.ymltest 環境設定で public_output_path: packs-test がコメントアウトされ、テスト環境での出力パスを本番環境と同じ packs に統一しました。config/webpack/environment.js の Sass 関数 image-url($path) は webpack エイリアスを使わず固定の相対パス /packs/media/${pathValue} を返すように変更されました。

Changes

ファイル/パス 変更概要
config/webpacker.yml test環境の public_output_path: packs-test をコメントアウトし、本番環境と同じ出力パスに統一
config/webpack/environment.js Sass関数 image-url($path) の画像URLを webpack エイリアス付きから固定の相対パスに変更

Possibly related PRs

Poem

テストの道はひとつに揃い、
packsの中でみんな集う。
画像の道もすっきり変わり、
うさぎは跳ねて喜ぶよ。
さあ、新しい風を感じて、
軽やかにコードを紡ごう!
🐇🌿✨


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 871df99 and 628a299.

📒 Files selected for processing (2)
  • config/webpack/environment.js (1 hunks)
  • config/webpacker.yml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • config/webpacker.yml
  • config/webpack/environment.js
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build_and_test
✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @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.

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.

Copy link
Copy Markdown

@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.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 42d52a4 and 23ee8e2.

📒 Files selected for processing (1)
  • config/webpacker.yml (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.37.1)
config/webpacker.yml

[error] 87-87: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build_and_test

machida and others added 2 commits July 18, 2025 19:17
Remove trailing spaces on line 87 and update comment to accurately
reflect the explicit public_path setting for test environment.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
Update image-url Sass function to generate correct paths based on
RAILS_ENV, using /packs-test/ for test environment and /packs/ for
production to resolve routing errors in tests.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@machida machida self-assigned this Jul 18, 2025
machida and others added 2 commits July 19, 2025 00:18
- Use same output path for test and production environments
- Simplify image-url function to use consistent /packs/media/ path
- Remove environment-specific path handling for better consistency

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
Changes the image-url() Sass function to use ~images/ alias instead of
absolute /packs/media/ paths. This allows Webpack to properly resolve
image files during build time while still allowing Rails asset host
configuration to apply the correct domain prefix in production.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@machida machida merged commit 6262861 into main Jul 18, 2025
2 checks passed
@machida machida deleted the image-path-css branch July 18, 2025 16:02
@github-actions github-actions bot mentioned this pull request Jul 18, 2025
87 tasks
This was referenced Nov 6, 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.

1 participant