I've come up against a bug with ActiveRecord when using namespaces models and polymorphic associations, it's a common use-case so should probably be fixed before a 4.2 release.

Error:

NoMethodError: undefined method `relation_delegate_class' for Comment:Module

Example:

class Post::Base < ActiveRecord::Base
  self.table_name = 'posts'
end

class Post::Special < Post::Base
  has

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

When an agent mute/unmute the converstion, add an activity message "#{agent_name} has muted the conversation"

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

The calculator should always return a BigDecimal, but that's not always the case.

For example the flat_rate calculator return 0 as Integer on the else branch.

If the calculator returns a type other than BigDecimal a warning will be issued by the adjustment action for the promotions,
for example