Add read-only Android question and answer browsing
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 68/100
Research direction
Start with internal/web/handler/questions.go, internal/question/, and the reader components from #84; review prerequisites #83 and #84 first. Add read-only question lists and details with bodies, answers, accepted-answer state, public URLs, route changes, and error or missing-resource handling. Test lists and details using synthetic answered and unanswered questions, including unauthenticated reading.
Written by the indexing model from the issue text.
Description
Roadmap: #76
Goal
Browse public questions and read their answers in the Android app.
Acceptance criteria
- Show question lists, question bodies, answers, and the server's accepted-answer state.
- Preserve public question URLs when opening or sharing content.
- Handle unanswered questions, missing resources, errors, and route changes.
- Keep reading available without an account.
- Test lists and details with synthetic answered and unanswered questions.
Start: internal/web/handler/questions.go, internal/question/, and reader components from #84. Authoring and vote mutations are separate tasks.
Prerequisites: #83, #84.
- Dominant language
- Go
- Stars
- 1
- Forks
- 7
- Avg merge
- 2h 19m
- Merged PRs (30d)
- 17
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
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
wavefnd/wave-platform#139 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 Half a day Newbie friendliness 88/100
wavefnd/wave-platform#137 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
wavefnd/wave-platform#136 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 1/5 Under an hour Newbie friendliness 94/100
wavefnd/wave-platform#135 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
wavefnd/wave-platform#133 ·
Maintainers usually reply within 1 day
All issues in wavefnd/wave-platform
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
DataDog/dd-trace-go#5469 ·
Maintainers usually reply within 1 day
-
bug tests
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
l3montree-dev/devguard#3101 ·
Maintainers usually reply within 1 day
-
area:*of bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oapi-codegen/oapi-codegen#2593 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 85/100
DaoCloud/DaoCloud-docs#7432 ·
Maintainers usually reply within 1 day