Preconfigure the test app to use Solid Queue/Mission Control - Jobs#3618
Preconfigure the test app to use Solid Queue/Mission Control - Jobs#3618taylor-steve wants to merge 3 commits intomainfrom
Conversation
jcoyne
left a comment
There was a problem hiding this comment.
I would encourage the community to skip this one. Although it does successfully show that Spotlight can work with solid queue, it adds more dependencies into testing and generally makes it more complicated. I think we can all agree that the engine is hard to maintain, so we should strive for simplicity.
|
@jcoyne thanks for the input. This is only for the test app, and only when not running in CI. Do you have an alternative approach to suggest to remove the burden of installing an active job backend for local developers? Are you opposed to the ask in general (to reduce this friction for new/less active devs), or only that it's touching test related code? I'm all for simplicity. |
|
@taylor-steve the test app is still used for doing tests locally. In this case we are adding complexity as we are running different code in the developers local tests than we are running in CI. That's the kind of thing that gets hard to understand when a problem arises. Isn't the asynchronous ActiveJob adapter already installed by default in rails? |
Description
This pre-configures Solid Queue/Mission Control - Jobs for the test app. This could be a potential quality of life improvement for developers. It's been brought up in the past that the behavior of jobs (e.g., indexing & indexing progress) can be confusing when using the test app for development without an Active Job backend installed & configured.
This is only for the test app in the development environment. It does not impact template installs.