A public way to add feature definitions to FeatureSet
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by reading FeatureSet, especially find_feature() and feature_tree(), then inspect caldav_server_tester/future_features.py to see how definitions are currently added. Done means a public register_features(definitions) method adds missing definitions, keeps caldav's definitions when names overlap, clears the relevant caches, and returns the names added.
由索引模型根据 Issue 内容生成。
描述
Disclaimer: AI-generated text below the line, generated by Claude Opus 5.5, from the prompt(s):
The problem is that the compatibility tree cannot be edited without also releasing the caldav library. However, this is big friction, perhaps we should find some workaround in 1.7.0. Like, having a FUTURE_FEATURES dict that contains not-yet-released changes in the caldav library, and then patch up
caldav.compatibility_hints.FEATURES |= FUTURE_FEATURES, could that work out?
A new probe in caldav-server-tester needs a feature definition in FeatureSet.FEATURES, and that can only change with a caldav release. To get past this, the tester now carries the definitions caldav has not released yet (FUTURE_FEATURES in caldav_server_tester/future_features.py) and adds them to FeatureSet.FEATURES when it is imported.
That works, but it depends on caldav internals: find_feature() caches subfeatures inside the definitions and feature_tree() caches _feature_tree, so the tester has to clear both, or a parent looked up before the patch never lists its new child.
Suggestion: a class method such as FeatureSet.register_features(definitions: dict) -> list[str] that adds the definitions caldav lacks, keeps caldav's own where both define a feature, clears the caches, and returns the names it added. The tester would then call that instead of patching the class.
- 主要语言
- Python
- 星标
- 412
- 派生
- 113
- 平均合并
- 9 小时 21 分钟
- 30 天内合并 PR
- 77
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
python-caldav/caldav 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 68/100
python-caldav/caldav#844 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
python-caldav/caldav#792 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
python-caldav/caldav#788 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
python-caldav/caldav#687 ·
维护者通常 1 天内回复
-
Objects built from arguments have a TZID but no VTIMEZONE可能已有人在做 @ivenos 今天认领。 未关闭
难度 4/5 3-5 天 新手友好度 45/100
python-caldav/caldav#849 · 14 条评论 ·
维护者通常 1 天内回复
查看 python-caldav/caldav 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
NVIDIA/auto-ontology#463 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
NousResearch/hermes-agent#151165 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
code-health
难度 2/5 1-3 小时 新手友好度 78/100
tinaudio/synth-setter#3750 ·
维护者通常 1 天内回复
-
[Bug] vllm-sr config migrate drops providers.models[].deployment可能已有人在做 @Bevisy 今天认领。 未关闭needs-acceptance wg/developer-experience-ecosystem
难度 2/5 1-3 小时 新手友好度 86/100
vllm-project/semantic-router#5996 ·
维护者通常 2 天内回复