Consider removing the dependency on ActiveSupport.
The con here is that Consult would lose access to the set of utility methods ActiveSupport provides, which are nice but Consult makes use of only 3 of these methods.
Removing ActiveSupport would mean one less dependency to manage and a smaller deployment package for projects that take a dependency on Consult.
Consider removing the dependency on ActiveSupport.
The con here is that Consult would lose access to the set of utility methods ActiveSupport provides, which are nice but Consult makes use of only 3 of these methods.
Removing ActiveSupport would mean one less dependency to manage and a smaller deployment package for projects that take a dependency on Consult.
Consult uses the following ActiveSupport methods:
String#present?
Hash#deep_symbolize_keys!
Hash#deep_merge
Worth ripping out?