Moving core_ext to within the squeel directory, to namespace it. There is a chance of conflicting paths with core_ext, which would either cause squeel core_ext not to load or the other core_ext not to load.
For example in our application we have Rails.root/lib as part of the autoload path and have a core_ext/hash for Hash within. Upon app boot we load load core_ext/hash before squeel has required core_ext/hash, so I assume ruby thinks the file has already loaded? This prevents the Hash extensions of squeel loading.
Namespacing the core_ext for the gem fixes this, similar to how ActiveSupport, jekyll and thor's core_ext are within the directory.
Moved core_ext to within squeel namespace.
There is a rare chance of conflicting paths with just core_ext/hash; this can
prevent squeel core extensions from be loaded, or prevent others from being
This seems fine. Thanks!