Did You Mean Versions Save

Internal Changes

• Use the frozen-string-literal pragma rather than calling .freeze everywhere
• Use the NameError#receiver method in DidYouMean:: ClassNameChecker to know the namespace where the constant call is made
• Refactored the SpellCheckerTest

Bug Fixes

• Fixed a bug where the gem doesn't install properly on Ruby 2.3.0dev

Features

• Now it corrects an instance variable name if the ivar name is mistyped and NoMethodError is raised:

  @number = 1
  @nubmer.zero?
  # => NoMethodError: undefined method `zero?' for nil:NilClass
  #
  #    Did you mean? @number
  #
  

• Support for JRuby 9.0.0.0

• Prefix-based correction (@tjohn, #50, #49)

• Correction search is about 75% faster than 0.9.10

Breaking Changes

• The ActiveRecord integration has been removed

Bug Fixes

• Fixed a bug where a duplicate "did you mean?" message was appended each time #to_s is called (@danfinnie, #51)

Features

• Order word suggestions based on Levenshtein distance (@tleish, #31)

Internal Changes

• Reduce memory allocation by about 40%
• Speed up Levenshtein distance calculation by about 40%
• The Java extension has been replaced with a pure JRuby implementation

Internal Changes

• Speed up Levenshtein by 50% and reduce 97% of memory usage

Bug Fixes

• Fixed an issue where did_you_mean doesn't install on JRuby properly.

Bug Fixes

• Fixed a bug where did_you_mean incorrectly suggests protected methods when it just isn't callable (@glittershark, #34)

Bug Fixes

• Whitelist #safe_constantize method from ActiveSupport::Inflector to avoid significant performance slowdown (@tleish, #19, #20)

Bug Fixes

• Fixed a bug where no suggestions will be made on JRuby