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
We use comments to label gems in our Gemfile (sometimes the use of a gem doesn't come easily from the name 😄) and this seems to stop the Pessimize parser from labeling subsequent gem lines. I've attached a sample Gemfile (and the Gemfile.backup) that triggers the issue. If I remove the ruby comment everything seems to work great.
Gemfile (after running pessimize):
# A sample Gemfilesource"https://rubygems.org"gem"rails","~> 4.2"gem"pessimize","~> 0.3"# Breaks heregem"devise"
Gemfile.backup:
# A sample Gemfilesource"https://rubygems.org"gem"rails"gem"pessimize"# Breaks heregem"devise"
The text was updated successfully, but these errors were encountered:
We use comments to label gems in our Gemfile (sometimes the use of a gem doesn't come easily from the name 😄) and this seems to stop the Pessimize parser from labeling subsequent gem lines. I've attached a sample Gemfile (and the Gemfile.backup) that triggers the issue. If I remove the ruby comment everything seems to work great.
Gemfile (after running
pessimize
):Gemfile.backup:
The text was updated successfully, but these errors were encountered: