Skip to content

Commit e0b0aa6

Browse files
committed
Remove the deprecation warning from the post-install message, as it's pretty old news now, and it's prominently displayed in the README.
1 parent 72f2b0e commit e0b0aa6

File tree

1 file changed

+1
-26
lines changed

1 file changed

+1
-26
lines changed

hamlbars.gemspec

+1-26
Original file line numberDiff line numberDiff line change
@@ -18,34 +18,9 @@ Gem::Specification.new do |s|
1818
s.add_development_dependency 'rake'
1919
s.add_development_dependency 'rspec', [">= 2.10.0"]
2020
s.add_development_dependency 'activesupport'
21-
21+
2222
s.files = %w(README.md History.md MIT-LICENSE) + Dir["lib/**/*"] + Dir["vendor/**/*"]
2323

2424
s.require_paths = ['lib']
25-
26-
s.post_install_message = <<-EOM
27-
DEPRECATION WARNING: Hamlbars 2.0 removes asset compilation!
28-
29-
Template compilation in Hamlbars was a major source of confusion and bugs
30-
since roughly half of its users are using Handlebars.js in their apps and
31-
the other half are using Handlebars as part of Ember.js.
32-
33-
Hamlbars now simply outputs the rendered HTML marked up with Handlebars
34-
sections. It is up to you to choose the Handlebars compiler that works
35-
for you.
36-
37-
If you're using Ember.js I would suggest adding ember-rails to your
38-
Gemfile.
39-
40-
If you're using Handlebars.js then I would suggest adding handlebars_assets
41-
to your Gemfile.
42-
43-
For both of the above gems you may need to rename your templates to
44-
`mytemplate.js.hbs.hamlbars` in order for the output of Hamlbars to be sent
45-
into the correct compiler.
46-
47-
Thanks for using Hamlbars. You're awesome.
48-
@jamesotron
49-
EOM
5025
end
5126

0 commit comments

Comments
 (0)