Chris Irish

I had the same problem. I knew of this gem from Mikel Lindsaar's RailsConf presentation, "Keeping Rails on The Tracks". But when I went to google for it I came...

A workaround for this (if you're using Capybara) is use Capybara in your email spec. Something like ``` page = Capybara::Node::Simple.new(current_email.body.encoded) expect(page).to have_link('Equipment', href: equipment_url(equipment.serial_number, host: 'portal.lvh.me')) ```

I'm seeing this also

@gregmolnar I'm not sure, i'm linking to master in our Gemfile. I'll see if i have time today to try 2.1.1

This seems to still be an issue, is there a workaround?

@kiskoza This was due to a upstream Rails bug with the last security patch, they were supposed to allow Symbol by default but didn't. It's since been patched. https://github.com/rails/rails/commit/05ae3faaf3779d53935ab983b75f2dc7c6dfb7fa

@robphillips Maybe dumb question here but, where does the local variable "file" come from in your custom displayExistingFile function?

I see this same behavior in a Rails 6.1.1 app

I'm running into this same issue. We have had an api for a while that was built specifically for mobile apps. Now we're trying to use Ember with Ember-Data and...

Just of note, it does appear you can do something like this in your action ``` ruby Rabl.configuration.include_json_root = true render json: @object Rabl.configuration.include_json_root = false ``` Not very sexy...