Skip to content

Combine workflow lint fix with privateOutputPath fix#896

Closed
justin808 wants to merge 4 commits intomainfrom
codex/supersede-891-892
Closed

Combine workflow lint fix with privateOutputPath fix#896
justin808 wants to merge 4 commits intomainfrom
codex/supersede-891-892

Conversation

@justin808
Copy link
Copy Markdown
Member

Summary

This combines the two dependent PRs so the private output path fix can pass lint and merge cleanly.

Closes #890.
Supersedes #891 and #892.

Validation

  • Not run locally: this workspace is Ruby 2.6.10 while the repo requires Ruby >= 2.7 for bundle-based checks.

ihabadham and others added 4 commits February 14, 2026 22:28
Fixes the Linting CI job that has been failing on main since these
workflow files were added with single-quoted strings and trailing
newlines.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
The private_output_path feature (PR #592) added the Ruby-side method but
not the JS-side computed property. This caused consumers like React on
Rails to always get undefined for config.privateOutputPath, breaking
config sync and producing false warnings on every build.

Follows the same pattern as config.outputPath: resolves the raw YAML
string to an absolute path.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
Verifies privateOutputPath is undefined when private_output_path is
absent from shakapacker.yml, using the same SHAKAPACKER_CONFIG override
pattern as the manifestPath tests.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Feb 15, 2026

Warning

Rate limit exceeded

@justin808 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 24 minutes and 5 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch codex/supersede-891-892

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Feb 15, 2026

Greptile Summary

This PR combines Prettier formatting fixes from #892 with the privateOutputPath JavaScript config fix from #891. The changes add a computed privateOutputPath property to the JavaScript config that mirrors the Ruby implementation, resolving the private_output_path YAML setting to an absolute path.

Changes

  • Applied Prettier formatting to workflow YAML files (quote style and trailing newlines)
  • Added privateOutputPath computed property in package/config.ts that resolves private_output_path to absolute path when configured
  • Added privateOutputPath?: string to the TypeScript Config interface
  • Added comprehensive tests covering both positive (with private_output_path set) and negative (without it) cases

The implementation correctly follows the pattern used for outputPath and maintains parity with the Ruby configuration.

Confidence Score: 5/5

  • This PR is safe to merge with minimal risk
  • Clean combination of two straightforward changes: formatting fixes and a well-tested feature addition that mirrors existing Ruby implementation. All changes are additive (no breaking changes), comprehensive test coverage included, and follows established code patterns.
  • No files require special attention

Important Files Changed

Filename Overview
package/config.ts Added computed privateOutputPath property that resolves private_output_path to absolute path
package/types.ts Added optional privateOutputPath property to Config interface
test/package/config.test.js Added positive and negative tests for privateOutputPath property

Flowchart

flowchart TD
    A[Load YAML Config] --> B{private_output_path set?}
    B -->|Yes| C[Resolve to absolute path]
    B -->|No| D[privateOutputPath = undefined]
    C --> E[config.privateOutputPath = resolve path]
    D --> F[Skip assignment]
    E --> G[Export config]
    F --> G
    
    style C fill:#90EE90
    style E fill:#90EE90
    style D fill:#FFE4B5
    style F fill:#FFE4B5
Loading

Last reviewed commit: 74d582b

@justin808
Copy link
Copy Markdown
Member Author

Superseded by #902. This PR failed due workflow-file validation, so the replacement keeps only the privateOutputPath fix and tests.

@justin808
Copy link
Copy Markdown
Member Author

Closing as superseded by #902.

@justin808 justin808 closed this Feb 15, 2026
@justin808
Copy link
Copy Markdown
Member Author

Clarification: this was superseded by #902 because workflow-file changes caused a Claude review workflow validation failure.

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.

Missing privateOutputPath computed property in JS config (private_output_path feature incomplete on JS side)

2 participants