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

`quick-comment-edit` - Issue with list item description fails on re-edit button press (10003)

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
领域
api, databases

调研方向

未指定任何 repository 文件或测试。先从所引用的 process-endpoint 文档以及现有的 {processID}:{version} 处理方式入手;在实现之前,明确 namespace 和分隔符规则、与已存储标识符的兼容性以及验收案例。

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

描述

repro for https://github.com/refined-github/refined-github/issues/10003


Description

[!NOTE]
For simplicity, : is used as separator in below description, but other character(s) combinations could be used.

Allow : as a prefix/namespace separator to allow categorization, such as measurement:distance, measurement:area, etc., which offers an abstract grouping of processes, with low impact on the actual API endpoints definition.

This nomenclature has been proposed in the past (see process endpoints under section https://docs.ogc.org/per/20-016.html#terradue-dapa).

The : should be handled properly to distinguish it from its similar use for {processID}:{version} referencing.

Furthermore, the : prefix should not be limited to one item, but should allow any amount of namespace definitions, such as dev:testbed:measurement:area.

Considerations

  • A :: may be considered to avoid possible clashes with {processID}:{version} or other remote/provider process IDs that could already employ : (itself using namespaces or URN as process IDs).
  • The specific pattern of ^(.*):(?P<MAJOR>[0-9]+)\.(?P<MINOR>[0-9]+)\.(?P<PATCH>[0-9]+)$ might be enough to distiguish :-namespaced from :-revisioned uses of the same separator.
  • The selected separtor should not introduce ambiguities/breaking behaviour with existing databases that store
    "identifier": "{processID}:{version}" of older revisions for direct access.

References

主要语言
没有语言数据
星标
13
派生
19
平均合并
1 分钟
30 天内合并 PR
2

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

refined-github/sandbox 的其他 Issue

查看 refined-github/sandbox 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

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