haml-rails forces cache_template_loading = false in development

[travisp]

While this is almost always the right choice as a default, it ignores any explicitly chosen configuration by the developer (e.g. if trying to check how something in the application is working when templates and digests are cached). Could we consider allowing other values if explicitly set in the development configuration?

[indirect]

Allowing config seems fine. (In the meantime, just use bundle edit haml-rails to temporarily change the gem.)

On Sat, Jul 4, 2015 at 9:47 AM, Travis Pew notifications@github.com
wrote:

While this is almost always the right choice as a default, it ignores any explicitly chosen configuration by the developer (e.g. if trying to check how something in the application is working when templates and digests are cached). Could we consider allowing other values if explicitly set in the development configuration?

Reply to this email directly or view it on GitHub:
#101