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

[Onboarding + Enrollments] Define CourseCheck response mapping

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

还没有人认领这个 Issue。

评估

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

调研方向

Read the generated SDK entry point at packages/sdk_dart/lib/src/generated/catalog.dart and the app configuration in lib/config.dart, then implement the wrapper in lib/onboarding/course_lookup.dart. Add MockClient coverage in test/course_lookup_test.dart for the listed responses and query parameters; done means those tests pass without network access and errors map to unavailable.

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

描述

onboarding

What to build

Translate the catalog’s course-check response into four results the setup screen can use. Distinguish an offered course, a known but unoffered course, an unknown code and unavailable information.

Files

  • lib/onboarding/course_lookup.dart (new file)
  • Starting example: lib/config.dart
    Code to add or extend: enum CourseCheck { offered, notOffered, unknown, unavailable }; CourseCheck mapCourseCheck(bool exists,bool? offered).

Steps

  1. Return unknown when exists is false. When exists is true, return offered for offered=true, notOffered for offered=false, and unavailable for offered=null.
  2. Put this in mapCourseCheck(bool exists, bool? offered) and add the four values to CourseCheck. This issue only translates the response; the following issue makes the catalog request.
  3. Check all four combinations. In particular, false/null must be unknown rather than unavailable.

Example

false/null → unknown;true/false → notOffered;true/true → offered.

Check it works

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

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 摘要。