You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue seems to be caused by setting frozen_string_literal: true on lib/haml/temple_engine.rb (#967), which breaks an implicit contract in the interface between these two gems.
Whether this is a bug best fixed in tilt or haml (or both, for best backwards-forwards compatibility) I don't know, but in any case, tilt's Tilt::HamlTemplate#precompiled_template expects strings returned from calls to Haml::TempleEngine to be not-frozen, because it calls #force_encoding on the returned string.
The text was updated successfully, but these errors were encountered:
Version: haml
master
branch (no release version yet), tested on commit e4a8be9.I produce the following stacktrace when precompiling haml template with
tilt
via a Sinatra application:This issue seems to be caused by setting
frozen_string_literal: true
onlib/haml/temple_engine.rb
(#967), which breaks an implicit contract in the interface between these two gems.Whether this is a bug best fixed in
tilt
orhaml
(or both, for best backwards-forwards compatibility) I don't know, but in any case,tilt
'sTilt::HamlTemplate#precompiled_template
expects strings returned from calls toHaml::TempleEngine
to be not-frozen, because it calls#force_encoding
on the returned string.The text was updated successfully, but these errors were encountered: