You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Zeitwerk has caused a few problems recently (#331, #341) as its behaviour is different to Ruby's regular require approach. This usually makes itself known once releases have been made and are being tested by projects that use this library. This could be avoided by making the gem (or at least the specs) use Zeitwerk, making the problems occur sooner.
The text was updated successfully, but these errors were encountered:
peteryates
changed the title
Make the libary use Zeitwerk internally
Make the library use Zeitwerk internally
Jun 27, 2022
Zeitwerk has caused a few problems recently (#331, #341) as its behaviour is different to Ruby's regular
require
approach. This usually makes itself known once releases have been made and are being tested by projects that use this library. This could be avoided by making the gem (or at least the specs) use Zeitwerk, making the problems occur sooner.The text was updated successfully, but these errors were encountered: