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
Ruby is weird about constants. If your gem defines class Foo and mine defines SomeNameSpace::Foo, yours will get loaded and mine won't. You'll get the nice warning warning: toplevel constant Foo referenced by SomeNameSpace::Foo, and accessing SomeNameSpace::Foo will actually just get Foo.
In this case, I have an existing class Pickups::TimeSlot which conflicts with your top-level TimeSlot class. If you add a namespace to your TimeSlot, though, it should resolve the issue.
The text was updated successfully, but these errors were encountered:
Ruby is weird about constants. If your gem defines class
Foo
and mine definesSomeNameSpace::Foo
, yours will get loaded and mine won't. You'll get the nice warningwarning: toplevel constant Foo referenced by SomeNameSpace::Foo
, and accessingSomeNameSpace::Foo
will actually just getFoo
.In this case, I have an existing class
Pickups::TimeSlot
which conflicts with your top-levelTimeSlot
class. If you add a namespace to yourTimeSlot
, though, it should resolve the issue.The text was updated successfully, but these errors were encountered: