Describe Problem
As I've been working on getting the repo's dependencies and build-chain dusted off (and portable via a devcontainer), I've run into problems getting the dummy Rails app to play nicely and reduce its overall dependencies and brittleness.
Suggest Changes
Stepping back from the problem: does mrujs need to have a dummy Rails app for testing? I think there's an argument to made that Mrujs is simply focused on the client-side of the equation. Instead of trying to keep a dummy Rails app in sync & up-to-date, we could write tests against the turbo javascript libraries.
Provide Examples
We do the same for cable_ready, so this should be feasible
Describe Problem
As I've been working on getting the repo's dependencies and build-chain dusted off (and portable via a
devcontainer), I've run into problems getting the dummy Rails app to play nicely and reduce its overall dependencies and brittleness.Suggest Changes
Stepping back from the problem: does
mrujsneed to have a dummy Rails app for testing? I think there's an argument to made thatMrujsis simply focused on the client-side of the equation. Instead of trying to keep a dummy Rails app in sync & up-to-date, we could write tests against theturbojavascript libraries.Provide Examples
We do the same for
cable_ready, so this should be feasible