Since any assets from this gem are added to the default or custom manifest files that get precompiled, there is no reason to have each individual asset file in this gem precompiled.
As an example, by including wysiwyg-rails, we have more than doubled the number of files that are precompiled, despite not loading any of the files directly through a script or link tag. We include specific assets in an existing CSS or JS manifest file. As an example, when running assets precompilation on our app, we had 591 files generated with wysiwyg-rails as is. By undoing the wysiwyg-rails precompile config, that came down to 225 files.
This is an unnecessary and unwanted side effect of #12, which should either be reverted and/or some alternative to turning off the default precompilation of all files through the gem.
Since any assets from this gem are added to the default or custom manifest files that get precompiled, there is no reason to have each individual asset file in this gem precompiled.
As an example, by including wysiwyg-rails, we have more than doubled the number of files that are precompiled, despite not loading any of the files directly through a script or link tag. We include specific assets in an existing CSS or JS manifest file. As an example, when running assets precompilation on our app, we had 591 files generated with wysiwyg-rails as is. By undoing the wysiwyg-rails precompile config, that came down to 225 files.
This is an unnecessary and unwanted side effect of #12, which should either be reverted and/or some alternative to turning off the default precompilation of all files through the gem.