Make YAML Configuration and Rails Config Equivalent

[allcentury]

For matt_accessor's that are settable, I am unable to set some of these in config.yml.

For example, silence_polling in development:

development:
  <<: *default
  silence_polling: true

I'm unable to find the exact problem but happy to put in a fix if someone can point me in the right direction. Maybe here, but I don't see how is this line called?

[rosa]

Hey @allcentury, sorry for the confusion! All the settings in this section can be set in your config/application.rb file or in your environment specific file (such as development.rb), or in an initializer for Solid Queue alone. For example, in your application.rb file, you'd include something like:

config.solid_queue.silence_polling = true

[allcentury]

Thanks @rosa! Having some values settable in application.rb and others set in config.yaml is a confusing developer experience. I would think they would have parity

[rosa]

Hey @allcentury, the configuration in solid_queue.yml is for specific workers and dispatchers, whereas the configuration options set via config.solid_queue are for the Solid Queue's engine. Having these separate is a common pattern in Rails. For example, Active Storage's engine configuration options vs. Active Storage's specific storage service configuration. I'll make this clearer in the README.