Ollie Bennett

Hey @alessio-signorini this gem is no longer maintained; the [CanCanCan](https://github.com/CanCanCommunity/cancancan) gem is a compatible continuation of this gem and is also MIT licenced.

Hey @trptcolin I wonder if you've got any thoughts on this. Is the solution a whitelist we can configure somewhere? Happy to have a stab at it if you could...

Awesome, thanks for that! Works for us. I wrapped the initializer code with ```ruby # config/initializers/consistency_fail_workaround.rb if Object.const_defined?(:ConsistencyFail) # ... code from above end ``` to avoid `uninitialized constant` issues...

I also found disproportionate memory usage for this gem; `twilio-ruby (5.23.0)` is taking up 18% of the memory of my application (with ~100 direct gem dependencies in our project). ```...

Please could you share a little more context / code? What are you trying to delete, and how? Via the rails_admin UI?

Apologies - it seems the same thing has been asked in https://github.com/ledermann/rails-settings/issues/55. Any suggestions for improvements or implementation considerations much appreciated.

If alternative database storage types were used as suggested in #83 (`json`) or #40 (`hstore`), the query could be better structured (using `@>` operator, for instance).

Does a normal call (such as `@record.settings(:some_configured_type)`) work? Interested to see whether there's a general problem with the gem loading or whether it's specific to the `default_settings` hash. Which gem...

That's strange... - Have you restarted the server (or `spring` for example) after installing the gem? - Have you configured the relevant `default` values in `has_settings`? Here's my user config;...

Yep I'm not sure deeply nested `defaults` are supported. You might need to workaround your problem and consider ```ruby has_settings do |s| s.key :conecction, :defaults => { :user => '',...