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

Currently json and jsonb rails record attribute types will work, except that the dummy value will not be initialized if the schema specifies a default type. In other words lets say your migration specifies that a json column should have a default value of {abc: 12}. The HyperModel behavior should load the dummy value while waiting for the server to return with {abc: 12} instead it loads

Enhancement request:
The stylesheet_engine options are limited to :css, :sass and :scss. It would be nice to update or create a config option with the sole purpose of creating a pcss file when generating a new component.

When user added a new email template old template version must be exist and usable.