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

[Sessions: create / edit / cancel] Cancel through status-only update

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

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
50/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
dart, sql
领域
database, mobile

调研方向

Start with cancelSession in lib/sessions/session_repository.dart, and read the server guard at supabase/schemas/private/functions/sessions_guard_update.sql to see how cancellation timestamps are set. Read issue #29 first, since this issue builds on it. Done means the cancel call sends only a status update filtered by id and hostId, an already-cancelled session is treated as success on retry, and missing or unauthorized sessions raise a readable error. Verify with test/sessions/session_repository_dp_s09_test.dart, flutter test on that file, and flutter analyze.

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

描述

sessions

What to build

Cancel a hosted meeting by changing its status, not deleting it. The server supplies the cancellation timestamp, and retrying an already-completed cancellation should be handled safely.

Files

Steps

  1. Update {"status":"cancelled"} only, filtered by id and hostId.
  2. Do not delete row or set cancelledAt; server guard supplies timestamp. For session_cancelled, re-read own row and treat an already-cancelled state as satisfied.
  3. Unknown/missing/permission errors fail with a readable cancellation error.

Example

Request body contains only status; already cancelled row does not become a second update/delete.

Check it works

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

Before starting

  • #29 — Read caller hosted sessions

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

更多 Databases Issue

把新 issue 发到你的邮箱

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