[Request] Migrate to a better API
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue names no files, tests, or entry points. Start by locating the existing API and its threat-detection callers; clarify the result representation and coroutine/Flow contract before implementation. Done is an agreed, tested replacement API covering transparent errors and asynchronous use.
Written by the indexing model from the issue text.
Description
Request Statement
In order to achieve transparent error handling and better Async api, a new api is required.
Solution brainstorm
- use enum / struct / data class to communicate result of threat detection
- implement async api using coroutines & flows
- Dominant language
- Kotlin
- Stars
- 8
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
go 🏃 testing 🧪
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
valkey-io/valkey-glide#7239 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ethereum-lists/chains#8788 ·
Maintainers usually reply within 1 day
-
unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
thunderbird/thunderbird-android#11654 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tauri-apps/tauri#16173 ·
Maintainers usually reply within 2 days
-
feature
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day