[Report & Block] Map report response/error outcomes
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 半天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- dart, flutter, typescript
调研方向
Start in lib/moderation/report_client.dart, where reportErrorMessage(int status, String? code) is to be added, and check the Supabase function handler it is modeled on. Confirm that prerequisite #34 is merged first, since this extends its file. Done means the status-to-message mapping in the steps passes test/moderation/report_client_dp_r01_2_test.dart, and flutter analyze is clean.
由索引模型根据 Issue 内容生成。
描述
What to build
Turn reporting failures into safe messages students can act on. A received-report confirmation must appear only after the service accepts the report, not after a failed or limited request.
Files
lib/moderation/report_client.dart(extend the prerequisite’s file)- Starting example: supabase/functions/report/handler.ts
Code to add or extend:String reportErrorMessage(int status,String? code).
Steps
- Map401→Sign in again.;403→Reports are unavailable for this account.;404→This content is unavailable.;429→Please wait before reporting again.;502/503→Reporting is temporarily unavailable.
- 400 self-report/invalid input yields readable validation error, unknown generic fallback.
- Keep form input on every failure; no raw secret/error body.
Example
429 does not claim receipt;201 only means an accepted report, not moderation action.
Check it works
In test/moderation/report_client_dp_r01_2_test.dart, check the example above and the failure or limit described in the steps. Run flutter test test/moderation/report_client_dp_r01_2_test.dart and flutter analyze.
Before starting
- #34 — Send reports through DogPack report function
References
Assign yourself before starting, or comment to claim the issue. Project setup.
- 主要语言
- PLpgSQL
- 星标
- 0
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
DevDogsUGA/DogPack 的其他 Issue
-
polish
难度 2/5 1-3 小时 新手友好度 72/100
DevDogsUGA/DogPack#131 ·
-
polish
难度 2/5 1-3 小时 新手友好度 65/100
DevDogsUGA/DogPack#130 ·
-
moderation
难度 2/5 1-3 小时 新手友好度 75/100
DevDogsUGA/DogPack#119 ·
-
moderation
难度 2/5 1-3 小时 新手友好度 85/100
DevDogsUGA/DogPack#113 ·
-
discover
难度 2/5 1-3 小时 新手友好度 74/100
DevDogsUGA/DogPack#106 ·
查看 DevDogsUGA/DogPack 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
EmbarkStudios/cargo-deny#910 ·
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
OpenIntegrationEngine/engine#496 ·
维护者通常 1 天内回复
-
documentation glm5 llm-model
难度 2/5 1-3 小时 新手友好度 78/100
vllm-project/vllm-ascend#19062 ·
维护者通常 1 天内回复
-
author-page correction
难度 2/5 1-3 小时 新手友好度 68/100
acl-org/acl-anthology#10496 · 1 条评论 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 67/100
维护者通常 1 天内回复