Rails

Summary

Thanks to all the contributors.

Currently, the default HTTP Request Header includes X-Download-Options, which is the one used by IE. (ref: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers)
Rails 7 contains a lot of changes that are supposed to make IE unsupported, and I think it's not necessary to leave X-Download-Options as the default as well.

Since default_headers

lengthy canned responses make the canned responses page scroll horizontally, avoid this.

Problem this feature will solve

Given:

FactoryBot.define do
  user(factory: :author) { association(:author, role: role) }
end

DefinitionProxy#method_missing will declare the [association](https://github.com/thoughtbot/factory_bot/blob

I'm sorry to post an issue that is missing crucial evidence, but some debugging of a recent config loading bug makes me suspect that the react-rails railtie.rb may be modifying the load order of initializers, and preventing the values in Rails.application.config being as expected.

Whether this happens or not appears to be partly dependent on where in the Gemfile the react-rails gem is l

I'm not sure if this is the right approach and maybe I've not understood this new part of the pipeline, yet, but:

Suppose, the major part of the app code lives inside a rails engine including all javascripts. And there are several main apps using that engine. The main apps only contain some layout changes and some minor patches.

Therefore, in order to integrate the webpacker gem into this se

We have a problem: if files aren't loaded/required we don't have branch data. If they are added through track_files we give it 0/0 branches which we show as 100% coverage (all possible branches are covered).

That math is "wrong" though here because there are branches but we don't know what they are. We should probably count total branches here as "unkown" and establish that in our "math unive