Rails

As a followup to rails/rails#41722 we need a linter to make sure that any new code going into rails/rails fails a rubocop rule if it does not use OpenSSL::Digest and instead uses Digest.

Context

On mobile devices, footer section text should be adjusted to the center, contrary to the desktop where it is adjusted to the left.
Please refer to the screenshot attached.

Expected Behavior

Store name should be adjusted to the center of the footer on mobile devices.

Actual Behavior

The store name is not adjusted to the center of the footer on mobile devices.

Steps

https://sentry.io/share/issue/60a543b58ab747fdbd1873df1d0cc3b6/

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

Steps to Reproduce the Problem

If buffalo fails midway through generating a resource it does not undo what it has done in app.go. This is a very minor issue and was easy to resolve by deleting the duplicated resources from app.go. If I wasn't so new to go I'd be attempting to see if I could make a PR to fix this issue.

![screen shot 2018-04-18 at 10 09 49 am](https://user-images.git

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

A while ago, we converted API controller specs into requests specs, see #2052. But those specs still have references from their old "life" that we can clean a little bit with a small effort.

In fact, their filenames still have the _controller_ part, which makes no sense now. Eg. solidus/api/spec/requests/spree/api/addresses_controller_spec.rb

Also, they contain references to the previo