Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Report & Block] Delete a caller-owned block

未关闭
#115 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
55/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
dart, flutter, supabase
领域
backend

调研方向

Start with supabase/schemas/dogpack/tables/blocks.sql to confirm the blockerId and blockedId columns, then open lib/moderation/block_repository.dart, where the prerequisite issue #35 insert code should already live. Add unblockUser as a delete filtered by both eq conditions, treating zero affected rows as success. Done when test/moderation/block_repository_dp_r03_2_test.dart passes under flutter test and flutter analyze is clean.

由索引模型根据 Issue 内容生成。

描述

moderation

What to build

Remove a block placed by the current student. Match both people’s IDs and never remove a block that someone else placed against them.

Files

  • lib/moderation/block_repository.dart (extend the prerequisite’s file)
  • Starting example: supabase/schemas/dogpack/tables/blocks.sql
    Code to add or extend: Future<void> unblockUser(client,blockerId,blockedId).

Steps

  1. Delete from dogpack.blocks with both eq("blockerId", blockerId) and eq("blockedId", blockedId).
  2. Treat an already-missing row as a successful repeated unblock. Let network/permission failures reach the screen so the entry remains visible.
  3. Check both filters; never delete a block someone else placed against the student.

Example

Request has both conditions; repeated unblock succeeds with zero affected rows.

Check it works

In test/moderation/block_repository_dp_r03_2_test.dart, check the example above and the failure or limit described in the steps. Run flutter test test/moderation/block_repository_dp_r03_2_test.dart and flutter analyze.

Before starting

  • #35 — Insert a caller-owned block

References

Assign yourself before starting, or comment to claim the issue. Project setup.

主要语言
PLpgSQL
星标
0
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

DevDogsUGA/DogPack 的其他 Issue

查看 DevDogsUGA/DogPack 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。