示例
Show that Zeitwerk reload support is opt-in before setup and that `unload` is intentionally ineffective until then.
sha256:2a90ce3c040d689d13a78f69612cc42ce3d1451ba0e44e9418dd497a657ab283
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Show that Zeitwerk reload support is opt-in before setup and that `unload` is intentionally ineffective until then. HOW
- 包
- zeitwerk 2.8.3
- 环境
- ruby
- 创建时间
- 2026-08-17T02:49:45Z
常见的想当然
Calling reload and unload-like operations is enough to refresh or remove constants, so explicit pre-setup reloading configuration should not matter.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- assert a loader without `enable_reloading` raises `Zeitwerk::ReloadingDisabledError` on `reload` after `setup`, and then `unload` keeps a previously loaded constant in place
- assert enabling reloading after `setup` raises `Zeitwerk::Error` and leaves `reloading_enabled?` false
- assert enabling reloading before `setup` makes `unload` remove a loaded constant so that the next reference is a `NameError`
文件
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- fixtures/noreload/no_reload_widget.rb
- fixtures/reload_after/reload_after_widget.rb
- fixtures/reload_enabled/reload_enabled_widget.rb
- fixtures/reloadable/with_reload_widget.rb
- test/contract.rb
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9