feat(search): add Recently Updated sort option (closes #392)#520
feat(search): add Recently Updated sort option (closes #392)#520rainxchzed merged 2 commits intomainfrom
Conversation
WalkthroughThe pull request adds a "Recently Updated" sort option to the search feature. The change spans domain model updates (new enum constant), presentation layer UI mappings, data layer backend integration, and release notes across 13 languages documenting the new capability. ChangesRecently Updated Sort Feature
Poem
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 6
🤖 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.
Inline comments:
In `@core/presentation/src/commonMain/composeResources/files/whatsnew/16.json`:
- Line 19: Update the release-note string that currently reads "Search now sorts
by Recently Updated — find repos with fresh stable releases first." to avoid
implying it prioritizes stable releases; replace it with wording that reflects
sorting by repository activity (updated_at), for example "Search now sorts by
Recently Updated — find repos with the most recent activity first." Locate and
edit the exact JSON value containing the original sentence to perform the
change.
In `@core/presentation/src/commonMain/composeResources/files/whatsnew/hi/16.json`:
- Line 19: The Hindi release-note string "सर्च अब 'हाल ही में अपडेट किया गया' के
अनुसार सॉर्ट कर सकती है — सबसे नई स्थिर रिलीज़ वाले रेपो पहले देखें।" in 16.json
is incorrect because the product sorts by repository activity (GitHub
sort=updated), not by newest stable release; update that string to state that
results are ordered by recent activity/last updated (e.g., mention "हालिया
गतिविधि" or "हाल ही में अपडेट किया गया" meaning repos with recent updates appear
first) so the wording reflects repository activity rather than stable-release
ordering.
In `@core/presentation/src/commonMain/composeResources/files/whatsnew/ja/16.json`:
- Line 19: Update the release-note string that currently reads
"検索で「最近更新」順の並べ替えに対応 — 最新の安定版リリースがあるリポジトリを先に表示します。" to state that the "最近更新" sort
orders by repository activity/last update (pushes/any updates), not by latest
stable release; apply the equivalent wording change to the same message key in
all locale files (English, Spanish, French, etc.) so they accurately reflect use
of GitHub's sort=updated behavior rather than releases.
In `@core/presentation/src/commonMain/composeResources/files/whatsnew/ko/16.json`:
- Line 19: Update the Korean text on line containing "검색에서 ‘최근 업데이트’ 정렬을 추가했습니다
— 최신 안정 릴리스가 있는 저장소를 먼저 보여줍니다." to accurately describe the behavior: state that
the sort uses GitHub's recent activity (sort=updated) and prioritizes
repositories with recent updates/activity rather than those with the latest
stable releases; replace the misleading phrase "최신 안정 릴리스가 있는 저장소를 먼저 보여줍니다"
with a phrase like "최근에 업데이트되거나 활동이 있었던 저장소를 먼저 보여줍니다" so the message reflects
the actual GitHub sort behavior in 16.json.
In `@core/presentation/src/commonMain/composeResources/files/whatsnew/pl/16.json`:
- Line 19: Replace the Polish release-note string "Wyszukiwarka sortuje teraz po
„Ostatnio zaktualizowane” — najpierw repozytoria z najświeższymi stabilnymi
wydaniami." with wording that correctly reflects sorting by repository
activity/updated_at, e.g. "Wyszukiwarka sortuje teraz po „Ostatnio
zaktualizowane” — najpierw repozytoria z ostatnią aktywnością (pole
updated_at)." Locate and update the exact string occurrence in the JSON so it no
longer mentions "stabilnymi wydaniami."
In `@core/presentation/src/commonMain/composeResources/files/whatsnew/tr/16.json`:
- Line 19: The current Turkish string "Arama artık 'Yeni Güncellenmiş' sırasıyla
sıralanabiliyor — en yeni kararlı sürümlere sahip depoları önce görün."
incorrectly mentions "kararlı sürüm"; update this JSON value in
core/presentation/src/commonMain/composeResources/files/whatsnew/tr/16.json to
state that sorting uses the repository's last updated timestamp (GitHub
updated_at) instead of stable release date — e.g., replace the sentence to
something like "Arama artık 'Yeni Güncellenmiş' sırasına göre sıralanabiliyor —
en son güncellenen depoları önce görün." ensuring the string precisely replaces
the existing text.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 1e3972e3-7b71-4f51-8da8-a773ad2878d0
📒 Files selected for processing (18)
core/presentation/src/commonMain/composeResources/files/whatsnew/16.jsoncore/presentation/src/commonMain/composeResources/files/whatsnew/ar/16.jsoncore/presentation/src/commonMain/composeResources/files/whatsnew/bn/16.jsoncore/presentation/src/commonMain/composeResources/files/whatsnew/es/16.jsoncore/presentation/src/commonMain/composeResources/files/whatsnew/fr/16.jsoncore/presentation/src/commonMain/composeResources/files/whatsnew/hi/16.jsoncore/presentation/src/commonMain/composeResources/files/whatsnew/it/16.jsoncore/presentation/src/commonMain/composeResources/files/whatsnew/ja/16.jsoncore/presentation/src/commonMain/composeResources/files/whatsnew/ko/16.jsoncore/presentation/src/commonMain/composeResources/files/whatsnew/pl/16.jsoncore/presentation/src/commonMain/composeResources/files/whatsnew/ru/16.jsoncore/presentation/src/commonMain/composeResources/files/whatsnew/tr/16.jsoncore/presentation/src/commonMain/composeResources/files/whatsnew/zh-CN/16.jsonfeature/search/data/src/commonMain/kotlin/zed/rainxch/search/data/repository/SearchRepositoryImpl.ktfeature/search/domain/src/commonMain/kotlin/zed/rainxch/domain/model/SortBy.ktfeature/search/presentation/src/commonMain/kotlin/zed/rainxch/search/presentation/mappers/SortByMappers.ktfeature/search/presentation/src/commonMain/kotlin/zed/rainxch/search/presentation/model/SortByUi.ktfeature/search/presentation/src/commonMain/kotlin/zed/rainxch/search/presentation/utils/SortByMapper.kt
| "Installer attribution — set what installer name silent installs claim, so apps that gate on installer source can be coaxed into running.", | ||
| "Manual refresh on details — pull-to-refresh on Android, overflow-menu Refresh on every platform, Ctrl/Cmd+R on desktop." | ||
| "Manual refresh on details — pull-to-refresh on Android, overflow-menu Refresh on every platform, Ctrl/Cmd+R on desktop.", | ||
| "Search now sorts by Recently Updated — find repos with fresh stable releases first." |
There was a problem hiding this comment.
Fix release-note claim to match actual sort behavior.
Line 19 currently says results prioritize repos with fresh stable releases, but this feature sorts by repository updated_at (recent activity). Please update the copy to avoid a misleading promise.
Proposed wording
- "Search now sorts by Recently Updated — find repos with fresh stable releases first."
+ "Search now sorts by Recently Updated — find repos with the most recent repository updates first."📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "Search now sorts by Recently Updated — find repos with fresh stable releases first." | |
| "Search now sorts by Recently Updated — find repos with the most recent repository updates first." |
🤖 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 `@core/presentation/src/commonMain/composeResources/files/whatsnew/16.json` at
line 19, Update the release-note string that currently reads "Search now sorts
by Recently Updated — find repos with fresh stable releases first." to avoid
implying it prioritizes stable releases; replace it with wording that reflects
sorting by repository activity (updated_at), for example "Search now sorts by
Recently Updated — find repos with the most recent activity first." Locate and
edit the exact JSON value containing the original sentence to perform the
change.
| "Installer attribution — साइलेंट इंस्टॉल किस इंस्टॉलर नाम का दावा करेंगे, इसे सेट करें ताकि इंस्टॉलर सोर्स पर निर्भर ऐप्स भी चल सकें।", | ||
| "विवरण स्क्रीन पर मैन्युअल रीफ़्रेश — Android पर पुल-टू-रीफ़्रेश, हर प्लेटफ़ॉर्म पर ओवरफ़्लो मेन्यू में 'रीफ़्रेश', डेस्कटॉप पर Ctrl/Cmd+R।" | ||
| "विवरण स्क्रीन पर मैन्युअल रीफ़्रेश — Android पर पुल-टू-रीफ़्रेश, हर प्लेटफ़ॉर्म पर ओवरफ़्लो मेन्यू में 'रीफ़्रेश', डेस्कटॉप पर Ctrl/Cmd+R।", | ||
| "सर्च अब 'हाल ही में अपडेट किया गया' के अनुसार सॉर्ट कर सकती है — सबसे नई स्थिर रिलीज़ वाले रेपो पहले देखें।" |
There was a problem hiding this comment.
Release-note claim on stable-release ordering is inaccurate.
Line 19 says this sort shows repos with the newest stable release first, but the implemented behavior is GitHub sort=updated (repository activity). Please reword to avoid mismatch with actual UX.
Suggested wording (Hindi)
- "सर्च अब 'हाल ही में अपडेट किया गया' के अनुसार सॉर्ट कर सकती है — सबसे नई स्थिर रिलीज़ वाले रेपो पहले देखें।"
+ "सर्च अब 'हाल ही में अपडेट किया गया' के अनुसार सॉर्ट कर सकती है — हाल की रिपॉज़िटरी गतिविधि (जैसे push/updates) वाले रेपो पहले देखें।"📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "सर्च अब 'हाल ही में अपडेट किया गया' के अनुसार सॉर्ट कर सकती है — सबसे नई स्थिर रिलीज़ वाले रेपो पहले देखें।" | |
| "सर्च अब 'हाल ही में अपडेट किया गया' के अनुसार सॉर्ट कर सकती है — हाल की रिपॉज़िटरी गतिविधि (जैसे push/updates) वाले रेपो पहले देखें।" |
🤖 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 `@core/presentation/src/commonMain/composeResources/files/whatsnew/hi/16.json`
at line 19, The Hindi release-note string "सर्च अब 'हाल ही में अपडेट किया गया'
के अनुसार सॉर्ट कर सकती है — सबसे नई स्थिर रिलीज़ वाले रेपो पहले देखें।" in
16.json is incorrect because the product sorts by repository activity (GitHub
sort=updated), not by newest stable release; update that string to state that
results are ordered by recent activity/last updated (e.g., mention "हालिया
गतिविधि" or "हाल ही में अपडेट किया गया" meaning repos with recent updates appear
first) so the wording reflects repository activity rather than stable-release
ordering.
| "インストーラー属性 — サイレントインストール時に名乗るインストーラー名を変更でき、インストール元を見るアプリも動かせるようにします。", | ||
| "詳細画面で手動更新 — Android はプルして更新、全プラットフォームでオーバーフローメニューに「更新」、デスクトップは Ctrl/Cmd+R に対応。" | ||
| "詳細画面で手動更新 — Android はプルして更新、全プラットフォームでオーバーフローメニューに「更新」、デスクトップは Ctrl/Cmd+R に対応。", | ||
| "検索で「最近更新」順の並べ替えに対応 — 最新の安定版リリースがあるリポジトリを先に表示します。" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Check all locale what's new files for version 16 to identify similar claims about "stable release" sorting
# Find all 16.json files in whatsnew directories
fd -e json '^16\.json$' --full-path 'whatsnew' --exec cat {} \; --exec echo "---" \;Repository: OpenHub-Store/GitHub-Store
Length of output: 166
🏁 Script executed:
git ls-files | grep whatsnew | head -20Repository: OpenHub-Store/GitHub-Store
Length of output: 1614
🏁 Script executed:
cat core/presentation/src/commonMain/composeResources/files/whatsnew/ja/16.jsonRepository: OpenHub-Store/GitHub-Store
Length of output: 1711
🏁 Script executed:
cat core/presentation/src/commonMain/composeResources/files/whatsnew/16.jsonRepository: OpenHub-Store/GitHub-Store
Length of output: 2379
🏁 Script executed:
cat core/presentation/src/commonMain/composeResources/files/whatsnew/es/16.json core/presentation/src/commonMain/composeResources/files/whatsnew/fr/16.jsonRepository: OpenHub-Store/GitHub-Store
Length of output: 5641
🏁 Script executed:
rg 'sort.*updated' --type json --type kotlin --type ts --type js -iRepository: OpenHub-Store/GitHub-Store
Length of output: 2937
🏁 Script executed:
cat -n feature/search/data/src/commonMain/kotlin/zed/rainxch/search/data/repository/SearchRepositoryImpl.kt | head -60Repository: OpenHub-Store/GitHub-Store
Length of output: 3029
🏁 Script executed:
rg -A 20 'RecentlyUpdated.*return null' feature/search/data/src/commonMain/kotlin/zed/rainxch/search/data/repository/SearchRepositoryImpl.ktRepository: OpenHub-Store/GitHub-Store
Length of output: 885
🏁 Script executed:
rg -B 5 -A 30 'sortBy == SortBy.MostForks || sortBy == SortBy.RecentlyUpdated' feature/search/data/src/commonMain/kotlin/zed/rainxch/search/data/repository/SearchRepositoryImpl.ktRepository: OpenHub-Store/GitHub-Store
Length of output: 16417
Fix release notes text — describes stable release sorting but feature actually sorts by any repository activity.
All locale files (English, Japanese, Spanish, French, etc.) claim that the "Recently Updated" sort shows "repos with fresh/latest stable releases first," but the implementation uses GitHub's REST API sort=updated parameter, which sorts by any repository update (pushes, not releases).
The backend intentionally skips RecentlyUpdated sorting and falls back to GitHub REST API, which natively honors the sort=updated parameter — this reflects the last push to any branch, not the latest stable release.
Update the release notes across all locales to clarify that the sort reflects repository activity/updates rather than specifically stable releases:
Example correction (Japanese)
- "検索で「最近更新」順の並べ替えに対応 — 最新の安定版リリースがあるリポジトリを先に表示します。"
+ "検索で「最近更新」順の並べ替えに対応 — 最近更新されたリポジトリを先に表示します。"Apply similar corrections to English, Spanish, French, and other locales.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "検索で「最近更新」順の並べ替えに対応 — 最新の安定版リリースがあるリポジトリを先に表示します。" | |
| "検索で「最近更新」順の並べ替えに対応 — 最近更新されたリポジトリを先に表示します。" |
🤖 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 `@core/presentation/src/commonMain/composeResources/files/whatsnew/ja/16.json`
at line 19, Update the release-note string that currently reads
"検索で「最近更新」順の並べ替えに対応 — 最新の安定版リリースがあるリポジトリを先に表示します。" to state that the "最近更新" sort
orders by repository activity/last update (pushes/any updates), not by latest
stable release; apply the equivalent wording change to the same message key in
all locale files (English, Spanish, French, etc.) so they accurately reflect use
of GitHub's sort=updated behavior rather than releases.
| "설치자 속성 — 무음 설치가 어떤 설치자 이름을 사용할지 지정해서, 설치 출처를 확인하는 앱도 실행될 수 있도록 합니다.", | ||
| "세부 정보 화면에서 수동 새로 고침 — Android에서 당겨서 새로 고침, 모든 플랫폼의 오버플로 메뉴에 ‘새로 고침’, 데스크톱에서 Ctrl/Cmd+R." | ||
| "세부 정보 화면에서 수동 새로 고침 — Android에서 당겨서 새로 고침, 모든 플랫폼의 오버플로 메뉴에 ‘새로 고침’, 데스크톱에서 Ctrl/Cmd+R.", | ||
| "검색에서 ‘최근 업데이트’ 정렬을 추가했습니다 — 최신 안정 릴리스가 있는 저장소를 먼저 보여줍니다." |
There was a problem hiding this comment.
Correct the sort description to match actual behavior.
Line 19 currently says the sort prioritizes repositories with the latest stable releases, but this feature uses GitHub sort=updated (recent repository updates/activity). Please adjust wording to avoid misleading users.
Suggested text update
- "검색에서 ‘최근 업데이트’ 정렬을 추가했습니다 — 최신 안정 릴리스가 있는 저장소를 먼저 보여줍니다."
+ "검색에서 ‘최근 업데이트’ 정렬을 추가했습니다 — 최근에 업데이트된 저장소를 먼저 보여줍니다."📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "검색에서 ‘최근 업데이트’ 정렬을 추가했습니다 — 최신 안정 릴리스가 있는 저장소를 먼저 보여줍니다." | |
| "검색에서 '최근 업데이트' 정렬을 추가했습니다 — 최근에 업데이트된 저장소를 먼저 보여줍니다." |
🤖 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 `@core/presentation/src/commonMain/composeResources/files/whatsnew/ko/16.json`
at line 19, Update the Korean text on line containing "검색에서 ‘최근 업데이트’ 정렬을 추가했습니다
— 최신 안정 릴리스가 있는 저장소를 먼저 보여줍니다." to accurately describe the behavior: state that
the sort uses GitHub's recent activity (sort=updated) and prioritizes
repositories with recent updates/activity rather than those with the latest
stable releases; replace the misleading phrase "최신 안정 릴리스가 있는 저장소를 먼저 보여줍니다"
with a phrase like "최근에 업데이트되거나 활동이 있었던 저장소를 먼저 보여줍니다" so the message reflects
the actual GitHub sort behavior in 16.json.
| "Atrybucja instalatora — ustaw nazwę instalatora, którą deklarują ciche instalacje, by aplikacje filtrujące po źródle instalacji działały.", | ||
| "Ręczne odświeżanie w szczegółach — pociągnij, aby odświeżyć na Androidzie, pozycja „Odśwież” w menu na każdej platformie, Ctrl/Cmd+R na pulpicie." | ||
| "Ręczne odświeżanie w szczegółach — pociągnij, aby odświeżyć na Androidzie, pozycja „Odśwież” w menu na każdej platformie, Ctrl/Cmd+R na pulpicie.", | ||
| "Wyszukiwarka sortuje teraz po „Ostatnio zaktualizowane” — najpierw repozytoria z najświeższymi stabilnymi wydaniami." |
There was a problem hiding this comment.
Correct the behavior description in Polish release notes.
Line 19 currently says sorting is by latest stable releases, but this feature sorts by repository recent updates/activity (updated_at). Please adjust wording to avoid misleading users.
Suggested wording update
- "Wyszukiwarka sortuje teraz po „Ostatnio zaktualizowane” — najpierw repozytoria z najświeższymi stabilnymi wydaniami."
+ "Wyszukiwarka sortuje teraz po „Ostatnio zaktualizowane” — najpierw repozytoria z najnowszą aktywnością (aktualizacjami)."📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "Wyszukiwarka sortuje teraz po „Ostatnio zaktualizowane” — najpierw repozytoria z najświeższymi stabilnymi wydaniami." | |
| "Wyszukiwarka sortuje teraz po „Ostatnio zaktualizowane" — najpierw repozytoria z najnowszą aktywnością (aktualizacjami)." |
🤖 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 `@core/presentation/src/commonMain/composeResources/files/whatsnew/pl/16.json`
at line 19, Replace the Polish release-note string "Wyszukiwarka sortuje teraz
po „Ostatnio zaktualizowane” — najpierw repozytoria z najświeższymi stabilnymi
wydaniami." with wording that correctly reflects sorting by repository
activity/updated_at, e.g. "Wyszukiwarka sortuje teraz po „Ostatnio
zaktualizowane” — najpierw repozytoria z ostatnią aktywnością (pole
updated_at)." Locate and update the exact string occurrence in the JSON so it no
longer mentions "stabilnymi wydaniami."
| "Yükleyici atfı — sessiz kurulumların hangi yükleyici adını taşıyacağını ayarlayın; kurulum kaynağını kontrol eden uygulamalar yine çalışsın.", | ||
| "Detaylar ekranında manuel yenileme — Android'de aşağı çek-yenile, her platformda taşma menüsünde 'Yenile' seçeneği, masaüstünde Ctrl/Cmd+R." | ||
| "Detaylar ekranında manuel yenileme — Android'de aşağı çek-yenile, her platformda taşma menüsünde 'Yenile' seçeneği, masaüstünde Ctrl/Cmd+R.", | ||
| "Arama artık 'Yeni Güncellenmiş' sırasıyla sıralanabiliyor — en yeni kararlı sürümlere sahip depoları önce görün." |
There was a problem hiding this comment.
“Kararlı sürüm” ifadesi davranışı yanlış temsil ediyor.
Bu metin, sıralamanın kararlı sürüm tarihine göre olduğunu söylüyor; PR kapsamındaki gerçek davranış ise GitHub updated_at (repo aktivitesi/push vb.) sıralaması. Kullanıcı beklentisini yanlış yönlendirmemek için metni buna göre düzeltelim.
Önerilen metin güncellemesi
- "Arama artık 'Yeni Güncellenmiş' sırasıyla sıralanabiliyor — en yeni kararlı sürümlere sahip depoları önce görün."
+ "Arama artık 'Yeni Güncellenmiş' sırasıyla sıralanabiliyor — yakın zamanda güncellenen depoları önce görün."📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "Arama artık 'Yeni Güncellenmiş' sırasıyla sıralanabiliyor — en yeni kararlı sürümlere sahip depoları önce görün." | |
| "Arama artık 'Yeni Güncellenmiş' sırasıyla sıralanabiliyor — yakın zamanda güncellenen depoları önce görün." |
🤖 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 `@core/presentation/src/commonMain/composeResources/files/whatsnew/tr/16.json`
at line 19, The current Turkish string "Arama artık 'Yeni Güncellenmiş'
sırasıyla sıralanabiliyor — en yeni kararlı sürümlere sahip depoları önce
görün." incorrectly mentions "kararlı sürüm"; update this JSON value in
core/presentation/src/commonMain/composeResources/files/whatsnew/tr/16.json to
state that sorting uses the repository's last updated timestamp (GitHub
updated_at) instead of stable release date — e.g., replace the sentence to
something like "Arama artık 'Yeni Güncellenmiş' sırasına göre sıralanabiliyor —
en son güncellenen depoları önce görün." ensuring the string precisely replaces
the existing text.
1 participant
Closes #392
Summary
Adds a fourth sort option to the Search tab — Recently Updated — surfacing repos with the freshest activity first. Maps to GitHub's
sort=updatedparameter, which orders by repo last-touched timestamp.What changed
SortByenum gainsRecentlyUpdated→"updated"GitHub sort param.SortByUienum gainsRecentlyUpdated;SortByBottomSheetpicks it up automatically (iteratesentries).RecentlyUpdated(backend only honorsrelevance/stars) — falls through to direct GitHub which natively supports the param.sort_recently_updatedalready existed in all 13 locale files (was prepared but never wired). Now reachable.Note
GitHub's
sort=updatedorders by repoupdated_at(any push), not strictly by latest stable release date. Closer-to-intent "sort by latest release" would need backend-side ranking and isn't shipped here — this lands the simple, native option that covers ~90% of the user's ask.Test plan
Summary by CodeRabbit
New Features
Documentation