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

Get eiffel JSON schemas from github instead

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

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
github, python
领域
api, backend

调研方向

首先定位库加载本地 Eiffel JSON schema 并验证事件的位置,然后检查在订阅期间如何选择事件版本。将该流程与 Eiffel repository 中的官方 schema 进行比较,并定义 HTTP 获取和缓存应如何工作;当无需发布新的库版本即可接受受支持的 schema 次要更新时,即表示完成。

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

描述

Description

Instead of hosting our own versions of the JSON schemas we should use the official schemas hosted on the eiffel repository.

Motivation

If a new version of an event is released and being sent, the eiffellib will not allow subscribers to that event.

Exemplification

The ArtifactCreated event gets updated from 4.0.0 to 4.0.1, a very minor release. A new version of the schema get published.
A publisher of that event starts publishing the 4.0.1 event, but the subscribers to that event do not update their eiffellib. This will mean that eiffellib will reject those events as there is no way to validate them.
In this case it was a very minor update and the subscribers would not be affected by the change, so it is quite annoying that eiffellib rejected it.

Benefits

Easier for subscribers of events to continue subscribing to that event, especially when there are only minor updates to the schemas.

Possible Drawbacks

Having to do HTTP requests, but the benefits of not having to update the entire chain on an eiffel specification update outweighs that completely.
Can be mitigated by having a cache in the library.

主要语言
Python
星标
8
派生
12
PR 合并指标
30 天内没有已合并 PR

环境准备

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

从这里开始

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

eiffel-community/eiffel-pythonlib 的其他 Issue

查看 eiffel-community/eiffel-pythonlib 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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