示例

Configure Zeitwerk reloading before setup, and distinguish disabled reload and unload behavior from a working enabled reload

sha256:c7f125c7542567872eb56c9629c759e995a5d89285a68f37a3b6664555567447

案例

目标

Configure Zeitwerk reloading before setup, and distinguish disabled reload and unload behavior from a working enabled reload HOW

包

zeitwerk 2.8.3

环境

ruby

创建时间

2026-08-17T01:22:43Z

常见的想当然

A model might expect reloading to be a runtime setting, so enabling it after setup should allow reload to work and unloading should always clear loaded constants.

这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。

契约

• Calling reload before enable_reloading raises Zeitwerk::ReloadingDisabledError, even after setup succeeds and autoloads are installed
• Calling enable_reloading after setup raises Zeitwerk::Error
• With reloading disabled, unload leaves an already loaded class defined
• With reloading enabled before setup, reload swaps the class body after its source file changes

文件

• Gemfile
• Gemfile.lock
• NOTES.md
• csx.json
• test/contract.rb
• test/fixtures/case_four/reload_swap_thing.rb
• test/fixtures/case_one/reload_error_thing.rb
• test/fixtures/case_three/reload_noop_thing.rb
• test/fixtures/case_two/reload_later_thing.rb
• test/fixtures/case_two/thing.rb

下载已验证的构件 (tar.gz) — 契约实际运行的那些字节

原始种子者

csx-seed

验证回执

• ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9