currently I am using version 1.2.0 which brings multi_json ~>1.0.3 to the dependency hull. now when I want to use something more recent (which includes Oj ) I need to monkey patch and copy+paste and still not sure if i missed some tiny details. somehow I just miss to "overrule" dependency constraints (because I know that 1.6.x is backward compatible to 1.0.x). bundler does not offer such feature. BUT with a more relax semantic version constraint like multi_json ~>1.0 I do have the chance to "overrule" things in case they are not backward compatible - something like multi_json >1.5
even if I know that dm-1.3.0 will not become true but being more relax with version constraints is maybe something considering for dm-2 ;)
currently I am using version 1.2.0 which brings multi_json ~>1.0.3 to the dependency hull. now when I want to use something more recent (which includes Oj ) I need to monkey patch and copy+paste and still not sure if i missed some tiny details. somehow I just miss to "overrule" dependency constraints (because I know that 1.6.x is backward compatible to 1.0.x). bundler does not offer such feature. BUT with a more relax semantic version constraint like multi_json ~>1.0 I do have the chance to "overrule" things in case they are not backward compatible - something like multi_json >1.5
even if I know that dm-1.3.0 will not become true but being more relax with version constraints is maybe something considering for dm-2 ;)