@joeldrapper I’ve seen this before with HAML - I’ve used it on some projects where I maintain the views, but then found it was an obstacle to getting a designer to work on the view layer
@joeldrapper Doesn’t it depend on team composition? I get the impression 37signals has designers editing the view templates as well, so staying close to HTML makes sense. For solo Rubyists or teams where the developers maintain the views, Ruby abstractions fit better.
@stevepolitodsgn Won’t that depend on whether (and how) you’re using ahoy.js to do client side page view tracking? Tracking events in controller actions would be triggered by InstaClick, but calling ahoy.trackView from the turbo:load event handler shouldn’t, should it?
@mscccc@julienbourdeau@rails Related to https://t.co/A8NdbiGLFS by any chance? I’ve used that on a couple of apps, but debugbar looks to provide more relevant detail for the development environment.
@GregMolnar@ryanstrickler describe is implemented in minitest/spec, but I don’t think you can just drop it into to the tests in a Rails app - minitest-spec-rails (and minitest-rails) do the work to add the spec bits into ActiveSupport::TestCase
@joemasilotti Yeah, I was thinking you could extend the PolicyResponse idea to carry the redirect url, or the data you’d use to determine it. It’s the basic idea of having policy methods that return data about the authorisation, instead of just being predicates.
@afomera The replicate gem from GitHub does this, but unfortunately it’s not been maintained for ages. It still worked last time I tried to use it though https://t.co/VoUgudXoki