#1875 fix: declare bash in pm.sh and check the sh dialect - #1887
#1875 fix: declare bash in pm.sh and check the sh dialect#1887RAprogramm wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe change updates ChangesShell dialect alignment
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Closes #1875.
Configs/.local/lib/hyde/pm.shdeclared#!/usr/bin/env shwhile using an indexed array (ARGS+=("$1"),"${ARGS[@]}") andlocalin 27 functions. It now declares bash, which is what the file needs and whathyde-shellalready runs it with. Running it directly on a system where/bin/shis dash stops being a syntax error.tests/test_shell.shgains the pass that could not be enabled while that file stood as it was: for every script whose shebang names sh, shellcheck must report noSC3xxxfinding. That family is the dialect one — a construct the declared shell does not have — and it sits below error severity, so the existing severity-filtered run never saw it. The comment that explained why the suite had to ignore the mismatch is replaced by one explaining what it now enforces.Verified with
sh tests/run.sh: 8 cases, 0 failed, 106 files parsed. The dialect pass reports as skipped here because shellcheck is not installed on this machine, so its first real run is CI.Summary by CodeRabbit
Bug Fixes
Tests
shthat use unsupported constructs.shdialect.