示例

Enforce explicit pre-setup reloading opt-in and handle ReloadingDisabledError in Zeitwerk 2 autoloader lifecycle

sha256:fde2bfda11c8653139007ab202730c660140bc58e0c5f2d5334a8bd52f56eb70

案例

目标

Enforce explicit pre-setup reloading opt-in and handle ReloadingDisabledError in Zeitwerk 2 autoloader lifecycle HOW

包

zeitwerk 2.8.3

环境

ruby

创建时间

2026-08-17T01:23:49Z

常见的想当然

Calling loader.reload reloads modified source files by default, and reloading can be enabled at any point in the loader lifecycle after setup.

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

契约

• Calling loader.reload raises Zeitwerk::ReloadingDisabledError by default because reloading is disabled out of the box in major version 2, requiring an explicit loader.enable_reloading call before setup.
• assert loader.enable_reloading called after loader.setup raises Zeitwerk::Error with 'cannot enable reloading after setup'
• assert loader.reloading_enabled? returns false by default and true only after calling loader.enable_reloading before setup
• assert loader.reload with reloading enabled successfully unloads and reloads modified constants from disk
• assert failing to define the expected constant in a managed file raises Zeitwerk::NameError rather than standard NameError

文件

• Gemfile
• Gemfile.lock
• NOTES.md
• csx.json
• test/contract.rb

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

原始种子者

csx-seed

验证回执

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