Skip to content

fix: restore the build by giving the Antigravity limit strings a French value - #219

Merged
chattymin merged 1 commit into
mainfrom
fix/french-antigravity-limit-strings
Aug 23, 2026
Merged

chattymin merged 1 commit into
mainfrom
fix/french-antigravity-limit-strings

Conversation

@chattymin

Copy link
Copy Markdown
Owner

Summary

main does not compile. t() takes a French argument now, and three Antigravity
limit strings still pass four:

Localization.swift:95:120: error: missing argument for parameter #5 in call
Localization.swift:96:148: error: missing argument for parameter #5 in call
Localization.swift:104:56:  error: missing argument for parameter #5 in call

The two changes never touched the same line, so git merged them without a conflict and
the branch reported clean. Its checks had run against a base that had no French column,
and nothing rebuilt the combined tree before it landed. Textual mergeability is not
build compatibility when one side widens a shared signature.

Changes

French for the three strings, matching the vocabulary already used elsewhere in the file
(Limite also appears in Limite atteinte, Limite de dépense personnelle):

String French
antigravityGeminiGroup Modèles Gemini
antigravityThirdPartyGroup Modèles Claude et GPT
antigravityWindow fallback Limite

No behaviour change beyond the missing translations.

Type of change

  • Bug fix
  • New feature
  • Refactor / cleanup
  • Documentation
  • Other:

Checklist

  • swift build and swift test pass locally — 766 tests, 9 skipped, 0 failures
  • PR title and description are written in English
  • No copyrighted assets, secrets, or private tooling references are committed (see CONTRIBUTING)
  • Tests were added or updated for this change — existing localization guards cover the strings; the compiler is the guard for argument count

…ch value

`t()` gained a French parameter, and the Antigravity limit-group strings landed
from a branch that predated it, so `main` stopped compiling: three calls still
pass four arguments.

The two branches merged cleanly because the conflict is semantic, not textual —
neither side edited the same line, and the pull request's checks had run against
a base without the French column.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@chattymin
chattymin merged commit 423dd9c into main Aug 23, 2026
2 checks passed
@chattymin
chattymin deleted the fix/french-antigravity-limit-strings branch August 23, 2026 14:57
cte13 pushed a commit to cte13/PokeTokenBar-iOS that referenced this pull request Aug 23, 2026
Brings in upstream features and integrates them with the fork's iOS/OpenCode Go work:
- Antigravity 2.0 / IDE official rate-limit tracking (chattymin#210, chattymin#219, chattymin#220)
- French (fr) UI language (chattymin#185) — added fr strings to fork-only labels
- Per-provider additional scan folders (chattymin#177/chattymin#187)
- Account-labeled official limits (chattymin#199), swift.org Swift 6.3 toolchains (chattymin#216),
  claude-fable-5 pricing (chattymin#198)

Conflicts resolved in Localization, UsageStore, PopoverView, and their tests by
keeping both the fork's OpenCode Go limits and upstream's Antigravity limits, and
by giving fork-only localized labels their French values.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
lukemonaghan pushed a commit to lukemonaghan/PokeTokenBar that referenced this pull request Aug 24, 2026
…ch value (chattymin#219)

`t()` gained a French parameter, and the Antigravity limit-group strings landed
from a branch that predated it, so `main` stopped compiling: three calls still
pass four arguments.

The two branches merged cleanly because the conflict is semantic, not textual —
neither side edited the same line, and the pull request's checks had run against
a base without the French column.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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