Kasper Timm Hansen
Kasper Timm Hansen
Currently, to get device specific tests users have to wrap their tests in `@@test_devices.each`, which kinda spills out implementation details to apps. Instead, we can add a `device_test` to abstract...
Since Bullet Train already ships with a task, it should know how to link all our appropriate gems adequately, and we don't need to burden apps as much with this....
All the assets and changes we need to integrate. bullet_train-core PR: https://github.com/bullet-train-co/bullet_train-core/pull/710 Pending: - [ ] Potential design changes - [ ] Fix CSRF issue when clicking on "-" to...
@andrewculver I think we should ship a v0.9.0 with the `p` deprecation, then we can merge #40 and prepare to ship v1.0.0, but give it a week for people to...
Once we've shipped the deprecation, we can merge this in later to remove `p` entirely.
First, we add a `turbo` helper in Rails views, so we can do: ```ruby Turbo::Elements::TurboStream.new(action: "morph", target: "post_1", view_context: self, partial: "posts/post", locals: { post: @post }) turbo.stream action: "morph",...
```ruby "showcase/previews/#{path.id}".classify "Showcase::Previews::Box".constantize.render_in(@view_context) # Require Zeitwerk naming conventions so `constantize` works. # showcase/previews/box.rb class Showcase::Previews::Box < Showcase::Phlex::Preview def template description do end sample "Basic" do end end end showcase.sample "Basic"...
Sometimes there's certain behavior you'd like to share between multiple objects. However, Associated Object's design was purposefully written to only support associating with one distinct class. This tries to shimmy...
Fixes https://github.com/bullet-train-co/bullet_train/issues/1663 We shouldn't replace the whole Rails' app's RouteSet, particularly when the `@routes` instance variable already provides the hook. Instead we can mirror what Rails does internally: https://github.com/rails/rails/blob/a59ddc714fa0403cbd8c7ae6abdec2f71ee7b63f/actionpack/test/controller/test_case_test.rb#L1224C1-L1236C8
Having your templates littered with `render "shared/fields/", form:, method:` and all the options managing doesn't feel very Rails-like. Since Rails already has an API built-in for extending the form builders...