fix: keep ficha and log on city screens between 64 and 90 columns (#7)

[blippip69]

fix: keep ficha and log on city screens between 64 and 90 columns (#7)

[gitar-bot]

💡 Quality: Unused cellW local variable left in mapScreen

The diff removed the mapW/tiles calculation that was the only consumer of the local const cellW = Math.max(1, m.cellW || CELL_W). The map pane is rendered with mapPane(m.map, w, h, { cellW: m.cellW }), which uses m.cellW directly and ignores the local clamped value, so cellW is now dead code. Remove the line to avoid confusion (and note the clamping/CELL_W fallback no longer applies here—if that fallback was intended for the pane, pass the local cellW to mapPane instead).

_{Was this helpful? React with 👍 / 👎}

[gitar-bot]

Code Review 👍 Approved with suggestions 0 resolved / 1 findings

Fixes sidebar and log visibility on city screens across 64 to 90 column layouts. Consider cleaning up the unused cellW local variable left in mapScreen.

💡 Quality: Unused cellW local variable left in mapScreen

📄 lib/render.js:1317

The diff removed the mapW/tiles calculation that was the only consumer of the local const cellW = Math.max(1, m.cellW || CELL_W). The map pane is rendered with mapPane(m.map, w, h, { cellW: m.cellW }), which uses m.cellW directly and ignores the local clamped value, so cellW is now dead code. Remove the line to avoid confusion (and note the clamping/CELL_W fallback no longer applies here—if that fallback was intended for the pane, pass the local cellW to mapPane instead).

🤖 Prompt for agents

Code Review: Fixes sidebar and log visibility on city screens across 64 to 90 column layouts. Consider cleaning up the unused cellW local variable left in mapScreen.

1. 💡 Quality: Unused `cellW` local variable left in mapScreen
   Files: lib/render.js:1317

   The diff removed the `mapW`/`tiles` calculation that was the only consumer of the local `const cellW = Math.max(1, m.cellW || CELL_W)`. The map pane is rendered with `mapPane(m.map, w, h, { cellW: m.cellW })`, which uses `m.cellW` directly and ignores the local clamped value, so `cellW` is now dead code. Remove the line to avoid confusion (and note the clamping/`CELL_W` fallback no longer applies here—if that fallback was intended for the pane, pass the local `cellW` to `mapPane` instead).

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

---

Important

Your trial ends in 7 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more.

_{Was this helpful? React with 👍 / 👎 | Gitar}

[leocagli]

Merged onto current main, the tests pass. npm run lint does not:

Checking formatting...
[warn] <the new test file>
[warn] Code style issues found in the above file. Run Prettier with --write to fix.

The repository runs prettier . --check as part of npm run lint, and CI runs
lint as its own job, so this alone turns the build red.

npm run format fixes it in one pass. Nothing else needs to change; the code itself
is fine.