| Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
| Name: ruby3.4-rubygem-zeitwerk | Distribution: openSUSE Tumbleweed |
| Version: 2.7.1 | Vendor: openSUSE |
| Release: 1.2 | Build date: Fri Dec 13 15:39:22 2024 |
| Group: Unspecified | Build host: reproducible |
| Size: 168613 | Source RPM: rubygem-zeitwerk-2.7.1-1.2.src.rpm |
| Packager: https://bugs.opensuse.org | |
| Url: https://github.com/fxn/zeitwerk | |
| Summary: Efficient and thread-safe constant autoloader | |
Zeitwerk implements constant autoloading with Ruby semantics. Each gem and application may have their own independent autoloader, with its own configuration, inflector, and logger. Supports autoloading, reloading, and eager loading.
MIT
* Fri Dec 13 2024 Aleksei Burlakov <aburlakov@suse.com>
- openSUSE:Factory doesn't support ruby3.2 --> don't limit to ruby3.2
* Wed Nov 06 2024 Dan Čermák <dcermak@suse.com>
- New upstream release 2.7.1
- limit building to ruby >= 3.2
* Fri Jun 21 2024 Dan Čermák <dan.cermak@posteo.net>
- New upstream release 2.6.16, no changelog found
* Tue Nov 14 2023 Dan Čermák <dan.cermak@posteo.net>
- New upstream release 2.6.12, no changelog found
* Wed Dec 07 2022 Stephan Kulow <coolo@suse.com>
updated to version 2.6.6
no changelog found
* Mon Oct 10 2022 Stephan Kulow <coolo@suse.com>
updated to version 2.6.1
no changelog found
* Wed Jun 15 2022 Manuel Schnitzer <mschnitzer@suse.com>
- updated to version 2.6.0
* Directories are processed in lexicographic order.
Different file systems may list directories in different order, and with this
change we ensure that client code eager loads consistently across platforms,
for example.
* Before this release, subdirectories of root directories always represented
namespaces (unless ignored or collapsed). From now on, to be considered
namespaces they also have to contain at least one non-ignored Ruby file with
extension `.rb`, directly or recursively.
If you know beforehand a certain directory or directory pattern does not
represent a namespace, it is intentional and more efficient to tell Zeitwerk
to [ignore](https://github.com/fxn/zeitwerk#ignoring-parts-of-the-project) it.
However, if you don't do so and have a directory `tasks` that only contains
Rake files, arguably that directory is not meant to represent a Ruby module.
Before, Zeitwerk would define a top-level `Tasks` module after it; now, it
does not.
This feature is also handy for projects that have directories with auxiliary
resources mixed in the project tree in a way that is too dynamic for an ignore
pattern to be practical. See https://github.com/fxn/zeitwerk/issues/216.
In the unlikely case that an existing project has an empty directory for the
sole purpose of defining a totally empty module (no code, and no nested
classes or modules), such module has now to be defined in a file.
Directories are scanned again on reloads.
* On setup, loaders created with `Zeitwerk::Loader.for_gem` issue warnings if
`lib` has extra, non-ignored Ruby files or directories.
This is motivated by existing gems with directories under `lib` that are not
meant to define Ruby modules, like directories for Rails generators, for
instance.
This warning can be silenced in the unlikely case that the extra stuff is
actually autoloadable and has to be managed by Zeitwerk.
Please, check the [documentation](https://github.com/fxn/zeitwerk#for_gem) for
further details.
This method returns an instance of a private subclass of `Zeitwerk::Loader`
now, but you cannot rely on the type, just on the interface.
* Tue Feb 15 2022 Stephan Kulow <coolo@suse.com>
updated to version 2.5.4
no changelog found
* Sat Jan 01 2022 Manuel Schnitzer <mschnitzer@suse.com>
- updated to version 2.5.3
* The change introduced in 2.5.2 implied a performance regression
that was particularly dramatic in Ruby 3.1. We'll address
[#198](https://github.com/fxn/zeitwerk/issues/198) in a different way.
* Wed Dec 29 2021 Manuel Schnitzer <mschnitzer@suse.com>
- updated to version 2.5.2
* When `Module#autoload` triggers the autovivification of an implicit
namespace, `$LOADED_FEATURES` now gets the correspoding directory
pushed. This is just a tweak to Zeitwerk's `Kernel#require` decoration.
That way it acts more like the original, and cooperates better with
other potential `Kernel#require` wrappers, like Bootsnap's.
* Tue Dec 21 2021 Manuel Schnitzer <mschnitzer@suse.com>
- updated to version 2.5.1
[#]# 2.5.1 (20 October 2021)
* Restores support for namespaces that are not hashable. For example namespaces that override the `hash` method with a different arity as shown in [#188](https://github.com/fxn/zeitwerk/issues/188).
[#]# 2.5.0 (20 October 2021)
[#]## Breaking changes
* Requires Ruby 2.5.
* Deletes the long time deprecated preload API. Instead of:
```ruby
loader.preload("app/models/user.rb")
```
just reference the constant on setup:
```ruby
loader.on_setup { User }
```
If you want to eager load a namespace, use the constants API:
```ruby
loader.on_setup do
Admin.constants(false).each { |cname| Admin.const_get(cname) }
end
```
[#]## Bug fixes
* Fixes a bug in which a certain valid combination of overlapping trees managed by different loaders and ignored directories was mistakenly reported as having conflicting directories.
* Detects external namespaces defined with `Module#autoload`. If your project reopens a 3rd party namespace, Zeitwerk already detected it and did not consider the namespace to be managed by the loader (automatically descends, ignored for reloads, etc.). However, the loader did not do that if the namespace had only an autoload in the 3rd party code yet to be executed. Now it does.
[#]## Callbacks
* Implements `Zeitwerk::Loader#on_setup`, which allows you to configure blocks of code to be executed on setup and on each reload. When the callback is fired, the loader is ready, you can refer to project constants in the block.
See the [documentation](https://github.com/fxn/zeitwerk#the-on_setup-callback) for further details.
* There is a new catch-all `Zeitwerk::Loader#on_load` that takes no argument and is triggered for all loaded objects:
```ruby
loader.on_load do |cpath, value, abspath|
[#] ...
end
```
Please, remember that if you want to trace the activity of a loader, `Zeitwerk::Loader#log!` logs plenty of information.
See the [documentation](https://github.com/fxn/zeitwerk#the-on_load-callback) for further details.
* The block of the existing `Zeitwerk::Loader#on_load` receives also the value stored in the constant, and the absolute path to its corresponding file or directory:
```ruby
loader.on_load("Service::NotificationsGateway") do |klass, abspath|
[#] ...
end
```
Remember that blocks can be defined to take less arguments than passed. So this change is backwards compatible. If you had
```ruby
loader.on_load("Service::NotificationsGateway") do
Service::NotificationsGateway.endpoint = ...
end
```
That works.
* Implements `Zeitwerk::Loader#on_unload`, which allows you to configure blocks of code to be executed before a certain class or module gets unloaded:
```ruby
loader.on_unload("Country") do |klass, _abspath|
klass.clear_cache
end
```
These callbacks are invoked during unloading, which happens in an unspecified order. Therefore, they should not refer to reloadable constants.
You can also be called for all unloaded objects:
```ruby
loader.on_unload do |cpath, value, abspath|
[#] ...
end
```
Please, remember that if you want to trace the activity of a loader, `Zeitwerk::Loader#log!` logs plenty of information.
See the [documentation](https://github.com/fxn/zeitwerk/blob/master/README.md#the-on_unload-callback) for further details.
[#]## Assorted
* Performance improvements.
* Documentation improvements.
* The method `Zeitwerk::Loader#eager_load` accepts a `force` flag:
```ruby
loader.eager_load(force: true)
```
If passed, eager load exclusions configured with `do_not_eager_load` are not honoured (but ignored files and directories are).
This may be handy for test suites that eager load in order to ensure all files define the expected constant.
* Eliminates internal use of `File.realpath`. One visible consequence is that in logs root dirs are shown as configured if they contain symlinks.
* When an autoloaded file does not define the expected constant, Ruby clears state differently starting with Ruby 3.1. Unloading has been revised to be compatible with both behaviours.
* Logging prints a few new traces.
/usr/lib64/ruby/gems/3.4.0/build_info /usr/lib64/ruby/gems/3.4.0/cache/zeitwerk-2.7.1.gem /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1 /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/MIT-LICENSE /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/README.md /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/core_ext /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/core_ext/kernel.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/core_ext/module.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/cref.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/error.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/explicit_namespace.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/gem_inflector.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/gem_loader.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/inflector.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/internal.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/loader /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/loader.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/loader/callbacks.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/loader/config.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/loader/eager_load.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/loader/helpers.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/null_inflector.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/real_mod_name.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/registry.rb /usr/lib64/ruby/gems/3.4.0/gems/zeitwerk-2.7.1/lib/zeitwerk/version.rb /usr/lib64/ruby/gems/3.4.0/specifications/zeitwerk-2.7.1.gemspec /usr/share/doc/packages/ruby3.4-rubygem-zeitwerk /usr/share/doc/packages/ruby3.4-rubygem-zeitwerk/MIT-LICENSE /usr/share/doc/packages/ruby3.4-rubygem-zeitwerk/README.md
Generated by rpm2html 1.8.1
Fabrice Bellet, Fri Oct 31 23:45:23 2025