aaif-goose / aaif-goose/goose-mobile
Set instructions in markdown files
- 主要言語
- Swift
- スター
- 163
- フォーク
- 33
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
Hi,
I went through the code and I noticed how the instructions are set.
I can't help but wonder if it wouldn't be simpler and cleaner to have the instructions set in their respective markdown files rather than hard coding them.
## Advantages
it would not only make the code more approachable but it would also help it make it scalable
## Solution
I'm thinking, achieving that in an optimized way, we would need to read the markdown files during the build process (as a Gradle task), that would set values to variables we can use at runtime.
コントリビューションガイド
調査の方向性
Look at the current hardcoded instructions in the Swift codebase. Identify the Gradle build configuration for the mobile project. Research how to read markdown files during a Gradle build task and pass those values as variables to the Swift runtime. The goal is to replace hardcoded strings with content loaded from markdown files.
索引モデルが issue の本文から書いたものです。
評価
- 領域
- build-system
- issue の種類
- リファクタリング
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 45/100