Data contract

[catreedle]

Contributor checklist

• This pull request is on a separate branch and not the main branch
• I have tested my code with the xcodebuild and swiftlint --strict commands as directed in the testing section of the contributing guide

---

Description

Changes for noun annotation:

• Add new directories: Data, DataContracts, DataManager in Scribe/Keyboards
• Add data-contracts from Scribe-Android (Scribe/Keyboards/DataContracts)
• Replace {lang}LanguageData.sqlite with the ones from Scribe-Android (Scribe/Keyboards/Data)
• Add new files ContractManager.swift, DataContract.swift, GenderManager.swift (Scribe/Keyboards/DataManager)
• Move LanguageDBManager.swift into Scribe/Keyboards/DataManager
• Update queryNounForm in LanguageDBManager to use data contract with helper functions in GenderManager
• Update Annotate.swift to add gender abbreviation conversion for wordAnnotation and autoActionAnnotation
• Bypass large file commit (.pre-commit-config.yaml)

Tested with noun annotations display correct genders

Changes for Plural command:

• Add PluralManager.swift to handle plural query logic based on data contracts (Scribe/Keyboards/DataManager)
• Update queryNounPlural in LanguageDBManager.swift to use data contract with helper functions in PluralManager
• Refactor queryDBRows in LanguageDBManager.swift to support multiple output columns instead of hardcoded "word" column
• Add queryAllPluralForms in LanguageDBManager.swift to preload all plural forms at keyboard startup
• Update Plural.swift to use preloaded pluralWords Set for "already plural" detection, replacing "isPlural" string approach
• Add pluralWords global variable declaration in InterfaceVariables.swift
• Initialize pluralWords Set in KeyboardViewController.swift loadKeys() function during first keyboard load
• Update wordAnnotation and autoActionAnnotation in Annotate.swift to check pluralWords Set for plural (PL) annotation
• Fix capitalization handling for languages with capitalized nouns (i.e, German) by always lowercasing for Set lookup in queryPluralNoun (Plural.swift)

Tested with:

• Feminine nouns (Spanish: casa → casas)
• Masculine nouns (Spanish: perro → perritos)
• Already plural detection (dogs, casas show "already plural" message)
• Capitalized German nouns (Männer correctly detected as already plural)
• Invalid input
• Plural annotations (PL) display correctly after successful pluralization

Related issue

• Convert Scribe-iOS over to using data contracts #585

[github-actions]

Thank you for the pull request! 💙

The Scribe-iOS team will do our best to address your contribution as soon as we can. If you're not already a member of our public Matrix community, please consider joining! We'd suggest that you use the Element client as well as Element X for a mobile app, and definitely join the General and iOS rooms once you're in. Also consider attending our bi-weekly Saturday dev syncs. It'd be great to meet you 😊

Note

Scribe uses Conventional Comments in reviews to make sure that communication is as clear as possible.

[github-actions]

Maintainer Checklist

The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

• Tests for changes have been written and the CI unit test, linting and formatting workflows within the PR checks do not indicate new errors in the files changed

• The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[andrewtavis]

Thanks so much for the PR, @catreedle! Let's discuss this a bit in the sync later today, and we'll try to bring this in tomorrow at the latest 😊

CC @henrikth93, @angrezichatterbox, @DeleMike 👋

[andrewtavis]

I'm reading Microsoft's Swift guide and they suggest always doing /// comments, at least for doc string. I think we can also do this at the file level. Let's plan on doing this in the future! I'll likely go through and fix this after we merge a few PRs in 😊

[andrewtavis]

Similarly here let's do /// docstring comments. I'll likely fix after so we don't need to worry about merge conflicts 😊

[andrewtavis]

No need for the - after // MARK: :)

[andrewtavis]

praise: This file was extremely easy to follow, @catreedle! Thanks for the great work :)

[andrewtavis]

praise: All's working really well here, @catreedle! So amazing to have this first step towards contracts coming in so we can use variable data :) Code is well thought out and we're removing what we don't need anymore.

note: Really sorry about the review time here :( Let's discuss in the sync if there's a way to make sure that we're getting you the support you need more consistently! Thanks for keeping at all of this!