Skip to content

chore: NSHighResolutionCapable as a real plist boolean, not <string>True</string>#1483

Merged
annejan merged 1 commit into
mainfrom
chore/plist-boolean-true
May 14, 2026
Merged

chore: NSHighResolutionCapable as a real plist boolean, not <string>True</string>#1483
annejan merged 1 commit into
mainfrom
chore/plist-boolean-true

Conversation

@annejan
Copy link
Copy Markdown
Member

@annejan annejan commented May 14, 2026

Summary

CodeRabbit's recurring nit on every new test subdir we add (most recently #1481): the `NSHighResolutionCapable` key in our `qtpass.plist` files is stored as `True` instead of the boolean `` form Apple's plist DTD expects. Sweep the project to fix it once so future per-subdir-PRs don't keep flagging it.

Files

11 plists touched (+1/-1 each):

  • `qtpass.plist` (root) — canonical, three symlinks point at it:
    • `main/qtpass.plist` -> `../qtpass.plist`
    • `tests/auto/ui/qtpass.plist` -> `../../../qtpass.plist`
    • `tests/auto/util/qtpass.plist` -> `../../../qtpass.plist`
  • 10 free-standing copies under `tests/auto/`: `configdialog`, `executor`, `exportpublickeydialog`, `filecontent`, `importkeydialog`, `keygendialog`, `model`, `passwordconfig`, `settings`, `trayicon`.

What this affects

These plists template the macOS `.app` bundle's `Info.plist`. No Linux/Windows impact, no test-runtime impact. Just correctness per Apple's DTD.

Out of scope

The duplicate `NSPrincipalClass` entry in `qtpass.plist` (lines 26-29) is a different pre-existing issue. Left alone.

Test plan

  • `make -j4` clean
  • `tests/auto/configdialog/tst_configdialog` — 11/11 (smoke that the test plist still parses)
  • No `True` left in any plist

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

  • Chores
    • Updated macOS application configuration settings to use proper boolean formatting across configuration files.

Review Change Stack

…rue</string>

CodeRabbit's recurring nit on every new test subdir we add: the
NSHighResolutionCapable key was being stored as <string>True</string>
instead of the boolean <true/> form Apple's plist DTD expects. Sweep
the project to fix it once.

11 plists touched:
- qtpass.plist (root, the canonical copy that main/qtpass.plist,
  tests/auto/ui/qtpass.plist, and tests/auto/util/qtpass.plist all
  symlink to)
- 10 free-standing copies in tests/auto/{configdialog, executor,
  exportpublickeydialog, filecontent, importkeydialog, keygendialog,
  model, passwordconfig, settings, trayicon}/qtpass.plist

Macros / templated values (CFBundleDisplayName etc.) untouched. No
build-time or run-time impact — these only feed the macOS .app bundle
Info.plist, but it makes future per-subdir nits go away.

NOT addressed: the existing duplicate <key>NSPrincipalClass</key> entry
in qtpass.plist (lines 26-29) is a different, pre-existing issue and
out of scope here.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 14, 2026

📝 Walkthrough

Walkthrough

This PR corrects the data type of the NSHighResolutionCapable macOS property list property from an incorrect string representation ("True") to the proper plist boolean type (true) across the main application configuration file and ten test configuration files.

Changes

Property list type corrections

Layer / File(s) Summary
NSHighResolutionCapable type corrections
qtpass.plist, tests/auto/configdialog/qtpass.plist, tests/auto/executor/qtpass.plist, tests/auto/exportpublickeydialog/qtpass.plist, tests/auto/filecontent/qtpass.plist, tests/auto/importkeydialog/qtpass.plist, tests/auto/keygendialog/qtpass.plist, tests/auto/model/qtpass.plist, tests/auto/passwordconfig/qtpass.plist, tests/auto/settings/qtpass.plist, tests/auto/trayicon/qtpass.plist
The NSHighResolutionCapable key is updated from a string value ("True") to the correct plist boolean type (true) in eleven configuration files to ensure proper type interpretation by macOS.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A plist tune, so clean and neat,
Eleven files made quite complete,
From strings that posed as booleans true,
Now proper types shine right on through,
High resolution, properly displayed,
In every config that we've made!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: converting NSHighResolutionCapable from a string literal to a proper plist boolean across the codebase.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/plist-boolean-true

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.

Copy link
Copy Markdown
Contributor

@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.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
qtpass.plist (1)

26-29: 🧹 Nitpick | 🔵 Trivial

Informational: Duplicate NSPrincipalClass key detected.

Lines 26-27 and 28-29 define the same key twice. While plist parsers typically use the last value, duplicate keys violate the plist specification. This is noted as out of scope for this PR but may warrant cleanup in a future change.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@qtpass.plist` around lines 26 - 29, The plist contains a duplicate key entry
for NSPrincipalClass with the same value NSApplication; remove the redundant
key/value pair so NSPrincipalClass appears only once (keep a single
<key>NSPrincipalClass</key> with its corresponding
<string>NSApplication</string>), ensuring the plist conforms to the spec and
avoids duplicate keys.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@qtpass.plist`:
- Around line 26-29: The plist contains a duplicate key entry for
NSPrincipalClass with the same value NSApplication; remove the redundant
key/value pair so NSPrincipalClass appears only once (keep a single
<key>NSPrincipalClass</key> with its corresponding
<string>NSApplication</string>), ensuring the plist conforms to the spec and
avoids duplicate keys.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Pro

Run ID: 990670c9-8257-419b-89c8-57482245b085

📥 Commits

Reviewing files that changed from the base of the PR and between 587cb9e and f77c3ed.

📒 Files selected for processing (11)
  • qtpass.plist
  • tests/auto/configdialog/qtpass.plist
  • tests/auto/executor/qtpass.plist
  • tests/auto/exportpublickeydialog/qtpass.plist
  • tests/auto/filecontent/qtpass.plist
  • tests/auto/importkeydialog/qtpass.plist
  • tests/auto/keygendialog/qtpass.plist
  • tests/auto/model/qtpass.plist
  • tests/auto/passwordconfig/qtpass.plist
  • tests/auto/settings/qtpass.plist
  • tests/auto/trayicon/qtpass.plist

@coveralls
Copy link
Copy Markdown

Coverage Status

coverage: 44.752%. remained the same — chore/plist-boolean-true into main

@annejan annejan merged commit 217c356 into main May 14, 2026
23 of 25 checks passed
@annejan annejan deleted the chore/plist-boolean-true branch May 14, 2026 00:10
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.

2 participants