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

[Report & Block] Render authorized host profile detail

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

还没有人认领这个 Issue。

评估

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

调研方向

Start with the schema in supabase/schemas/dogpack/tables/profiles.sql to see which columns are readable, then read the session code from #108 and the snapshot mapping from #26, since this issue depends on both. Create lib/screens/member_profile_screen.dart, query userId, displayName, classYear and major with the signed-in student's client using maybeSingle, and show an 'Profile unavailable' message when the result is null. Done when test/screens/member_profile_screen_dp_r04_test.dart passes for the authorized and unavailable cases and flutter analyze is clean.

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

描述

moderation

What to build

Show a host’s profile only when the current student is allowed to read it. An unavailable profile should show a neutral message instead of private fields or an invented name.

Files

Steps

  1. Select userId,displayName,classYear,major from profiles for target user with client using the signed-in student’s account/maybeSingle.
  2. Render visible plain snapshot, reporting/block callbacks with the target UUID; null produces Profile unavailable.
  3. Do not fetch via service key or show an invented host name.

Example

Authorized host Ada renders; hidden profile shows unavailable and no leaked fields.

Check it works

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

Before starting

  • #108 — Read authorized session detail
  • #26 — Map own profile to a plain snapshot

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

更多 Security Issue

把新 issue 发到你的邮箱

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