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

chore: resolve 23 pyright diagnostics and enable a pyright CI job

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
58/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
github-actions, python
领域
ci-cd, testing

调研方向

Start by running poetry run pyright and inspect the diagnostics in campus_python/__init__.py, assignments.py, oauth.py, and the named test files. Compare the configuration and CI approach with the nyxchange-timetable-v2 reference cited in the issue, then review .github/workflows/python-tests.yml. Done when the 23 diagnostics are resolved or deliberately ignored and a pyright CI job runs successfully.

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

描述

chore

Observation

With pyright's default exclude list restored (chore/pyright-exclude, PR #94), running pyright 1.1.414 against the repo reports 23 errors, 0 warnings in project code:

  • campus_python/ sources: __init__.py ×6, assignments.py ×2, oauth.py ×1 (reportArgumentType / reportAttributeAccessIssue / reportOptionalMemberAccess / reportCallIssue / reportReturnType)
  • tests: test_unauthorized_refresh.py ×6, test_campus_request.py ×2, test_audit.py ×1, plus 1 reportMissingImports (a test-side sys.path import, presumably)

Ask

Resolve the 23 diagnostics (or scope the config with per-file ignores where deliberate), then add a pyright job to .github/workflows/python-tests.yml following the nyxchange-timetable-v2 pattern (poetry run pyright with pyright as a dev dependency). This repo is the client every student app pins, so it should be the first place the gate lands.

Context

Found 2026-10-04 while applying the same exclude fix as nyxchange-timetable-v2#64 (PR #94). This repo currently gates on pytest only; the nyxchange fix (PR there: #66) is the reference for config + gate.

主要语言
Python
星标
0
派生
0
平均合并
35 分钟
30 天内合并 PR
43

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

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

nyjc-computing/campus-api-python 的其他 Issue

查看 nyjc-computing/campus-api-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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