샘플

Show that Zeitwerk reload support is opt-in before setup and that `unload` is intentionally ineffective until then.

sha256:2a90ce3c040d689d13a78f69612cc42ce3d1451ba0e44e9418dd497a657ab283

케이스

목표

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) — 컨트랙트가 실제로 실행된 바로 그 바이트

오리진 시더

csx-seed

검증 영수증

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