Skip to content

Investigate using Scribe contracts within Scribe-iOS #584

@andrewtavis

Description

@andrewtavis

Terms

Issue

This issue is a precursor to a larger issue that will follow that will convert Scribe-iOS over to using data contracts. Scribe-iOS as of now has a ton of hard coded operations to get data from the database based on which language keyboard is being used. This is problematic as it prevents the community from easily adding in new keyboards, and bloats the code with lots of conditions. Data contracts are a way to solve this, and have been being used in Scribe-Android from the start. Rather than complex conditions to for instance derive which conjugation view should be used and which fields should be used from the DB, we instead provide a JSON that can be used to derive what the conjugation tenses are as well as which fields should be used from the DB.

This issue would do the following:

  • Move the data and data_contracts directories over from Scribe-Android
    • Rename these directories to Data and DataContracts to be in line with iOS naming conventions
  • We can open a PR with these files in the repo as coding work for this issue
  • Investigate which files would need to change in order to switch the iOS application over to use contracts
    • Which files would need to change for noun annotations
    • The same for the plural command
    • The same for the translate command
    • The same for the conjugate command
    • The same for preposition annotations
  • A report will be written to explain all the files that need to be changed and a short summary of the changes needed in each file

Once this issue is finished, we can then proceed with #585 where the changes needed will be done😊

Metadata

Metadata

Assignees

Labels

help wantedExtra attention is neededquestionFurther information is requested

Type

Projects

Status

Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions