Add ActiveScheduler.config.{guard_with,queue_name_resolver} #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows configuration of a custom guard clause to check whether jobs should be wrapped or not, as well as allowing for a custom
queue_name_resolver
configuration which will be called to resolve the queue name when the queue is not configured. The idea behind this is to enable an option which avoids the use ofclass_name.constantize
, meaning that we don't have to load the entire Rails environment for the resque scheduler rake task and save some memory.Alternative to #22