Allow question authors to accept or clear an answer on Android
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 65/100
Research direction
Start with AcceptAnswerRequest and QuestionsHandler.Accept in internal/web/handler/questions.go, then trace the Android question screen and the prerequisites in #96 and #98. Verify the existing accept and clear contract before wiring the screen state. Done means the listed owner, non-owner, missing-answer, accept, replace, clear, failure, and duplicate-action cases are covered by tests.
Written by the indexing model from the issue text.
Description
Roadmap: #76
Goal
Expose the existing accepted-answer action in the Android question screen.
Acceptance criteria
- Show the action only when the current account is eligible; retain server authorization as the authority.
- Submit the answer ID to accept and the documented empty value to clear acceptance.
- Render the returned accepted state and handle switching to a different answer.
- Preserve current state on permission/network failure and prevent duplicate pending actions.
- Test owner, non-owner, missing-answer, accept, replace, and clear cases.
Start: AcceptAnswerRequest and QuestionsHandler.Accept in internal/web/handler/questions.go.
Prerequisites: #96, #98.
- Dominant language
- Go
- Stars
- 1
- Forks
- 7
- Avg merge
- 4h 19m
- Merged PRs (30d)
- 34
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from wavefnd/wave-platform
-
difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
wavefnd/wave-platform#472 ·
Maintainers usually reply within 1 day
-
difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 Half a day Newbie friendliness 86/100
wavefnd/wave-platform#471 ·
Maintainers usually reply within 1 day
-
difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 Half a day Newbie friendliness 88/100
wavefnd/wave-platform#470 ·
Maintainers usually reply within 1 day
-
difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
wavefnd/wave-platform#469 ·
Maintainers usually reply within 1 day
-
difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
wavefnd/wave-platform#468 ·
Maintainers usually reply within 1 day
All issues in wavefnd/wave-platform
Similar issues
-
bug go
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
genkit-ai/genkit#6761 · 1 comment ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 2 days
-
ready
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
kubeflow/pipelines#14784 · 1 comment ·
Maintainers usually reply within 2 days
-
bug frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
trust: update-propagation-directive requires developer mode while add and remove do notPossibly taken @bhuvan-somisetty claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days