Fix searchable queue configuration #840
Closed
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 PR fixes how the
Searchable
trait determines whether to queue jobs. Also, the published configuration file is updated to be compatible with the current version of the trait.The
Searchable
trait currently determines the queue connection and queue using the following two methods:However, the config file that is published by this package only contained the following config option:
This has been updated to the keys actually used by the trait:
Subsequently, another update to the
Searchable
trait itself was necessary, since this used the oldscout.queue
key to determine if jobs should be queued. It now correctly usesscout.queue.queue
:Edit: The same was done for the
queueRemoveFromSearch
method.