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

Cluster list ordering

未关闭
  • 哪里不对？
#137 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
70/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
typescript
领域
frontend

调研方向

The issue names no files, so start by finding where the cluster document list is sorted in this TypeScript web app. Keep the existing order (queued first, not-received last) and add sorting within those groups: RFCs-to-be by ascending RFC number, then drafts alphabetically. Done when cluster 496 renders in the order given in the example.

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

描述

enhancement

Lists of documents in a cluster are currently organized the following way (and this doesn't need to change):

  • documents that are in the queue are listed first
  • documents that have not been received are listed at the end

However, it would be helpful to further organize the documents by listing

  • RFCs-to-be first, sorted by ascending RFC number
  • draftstrings, alphabetized

For example, cluster 496 should be listed:

  • RFC-to-be 10066: draft-ietf-pce-multipath received
  • RFC-to-be 10067: draft-ietf-pce-sr-bidir-path received
  • RFC-to-be 10068: draft-ietf-pce-circuit-style-pcep-extensions received
  • draft-ietf-spring-cs-sr-policy blocked received
  • draft-ietf-idr-sr-policy-path-segment not received
  • draft-ietf-spring-sr-policy-yang not received
  • draft-ietf-spring-stamp-srpm-mpls not received
  • draft-ietf-spring-stamp-srpm-srv6 not received

Currently it looks like this:

Image
主要语言
TypeScript
星标
1
派生
4
30 天内没有已合并 PR

环境准备

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

从这里开始

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

ietf-tools/queue 的其他 Issue

查看 ietf-tools/queue 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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