summaryrefslogtreecommitdiff
path: root/lib/did_you_mean
AgeCommit message (Collapse)Author
2024-12-04[ruby/did_you_mean] Bump version to 2.0.0Yuki Nishijima
https://.com/ruby/did_you_mean/commit/1cce337962
2024-05-05[ruby/did_you_mean] Move development dependencies to GemfileNobuyoshi Nakada
https://.com/ruby/did_you_mean/commit/24c06dd509
2024-03-19[ruby/did_you_mean] Do not use #inspect to avoid unexpected performance ↵Yuki Nishijima
degradation closes https://.com/ruby/did_you_mean/pull/100 https://.com/ruby/did_you_mean/commit/bd11eefd6c
2024-03-16[ruby/did_you_mean] Avoid division for small length2Mau Magnaguagno
https://.com/ruby/did_you_mean/commit/cb518e251a
2024-03-16[ruby/did_you_mean] Remove Integer floor and prefix index from Jaro distanceMau Magnaguagno
The variable ``length2`` is an Integer, call to floor returns self. The variables ``i`` and ``prefix_bonus`` are equally incremented, no need to keep the ``i`` variable. https://.com/ruby/did_you_mean/commit/4408802289
2022-12-19[ruby/did_you_mean] Bump version to 1.6.3Hiroshi SHIBATA
https://.com/ruby/did_you_mean/commit/f7703add76
2022-12-05[ruby/did_you_mean] Do not suggest #name= for #name and vice versaMatthew Boeh
(https://.com/ruby/did_you_mean/pull/180) * Do not suggest #name= for #name and vice versa * Avoid allocating unnecessary MatchData Co-authored-by: Jean byroot Boussier <[email protected]> Co-authored-by: Jean byroot Boussier <[email protected]>
2022-12-05[ruby/did_you_mean] Bump version to 1.6.2Hiroshi SHIBATA
https://.com/ruby/did_you_mean/commit/f5b15128e2
2022-09-01[ruby/did_you_mean] Fixed correction duplicates in VariableNameCheckerImir Kiyamov
https://.com/ruby/did_you_mean/commit/c3fc412f6f
2022-06-07Manually merged https://.com/ruby/did_you_mean/pull/177Hiroshi SHIBATA
2022-05-20[ruby/did_you_mean] Fix `frozen_string_literal is ignored after any tokens` ↵Jean byroot Boussier
warning. (https://.com/ruby/did_you_mean/pull/172) ``` did_you_mean/formatters/verbose_formatter.rb:5: warning: `frozen_string_literal' is ignored after any tokens ``` https://.com/ruby/did_you_mean/commit/531760f323
2021-12-24Sync did_you_meanYuki Nishijima
2021-12-23Revert the commits for did_you_meanYuki Nishijima
This reverts commit feaf4fbc3fa16382fbd07158c448c7b5bdae78b5. This reverts commit 0d4bfbdbe1f880c712b3e60de5fce423e6096f8d. This reverts commit ac4e0978ee4358430396403065eabe1aca05784f.
2021-12-22* gems/default_gems: Sync did_you_meanYuki Nishijima
2021-12-21Revert commits for did_you_meanYuki Nishijima
This reverts commit 4560091b1c99ab33db0d653b9dd2d977fe4676d5. This reverts commit a6f76122a2395bd914daa0aa04fb5a6ce4e0c045. This reverts commit e59b18a6379c55f15ccda85c27d6997d44ef5293. This reverts commit 505dfae05d56d844ea150676edb87850a406d071.
2021-12-21* gems/default_gems: Sync did_you_meanYuki Nishijima
2021-10-22Sync did_you_mean againYuki Nishijima
2021-10-22Revert "Sync did_you_mean"Yuki Nishijima
This reverts commit e22d293e06966733e71a7fd9725eee06c03d0177.
2021-10-22Sync did_you_meanYuki Nishijima
2021-06-29Use String#include? instead of end_with? to avoid message duplicationYusuke Endoh
Previously, did_you_mean used `msg.end_with?(suggestion)` to check if its suggestion is already added. I'm now creating a gem that also modifies Exception's message. This breaks did_you_mean's duplication check. This change makes the check use String#include? instead of end_with?. https://.com/ruby/did_you_mean/commit/b35e030549
2021-06-29Let Correctable#original_message skip prepended method definitionsYusuke Endoh
Previously, DidYouMean::Correctable#original_message did `method(:to_s).super_method.call` to call the original to_s method by skipping Correctable#to_s. I'm now creating a gem that prepends another to_s method to NameError, which confuses the hack. An immediate solution is to replace it with `method(:to_s).super_method.super_method.call` to skip the two methods. But it is too ad-hoc. This changeset uses more extensible approach and allow a prepended module to declare that they should be skipped by defining a constant named `SKIP_TO_S_FOR_SUPER_LOOKUP`. https://.com/ruby/did_you_mean/commit/8352c154e3
2021-06-29Should require "rbconfig" to use RbConfigNobuyoshi Nakada
https://.com/ruby/did_you_mean/commit/fbe5aaaae8
2021-06-29Start v1.6.0 developmentYuki Nishijima
https://.com/ruby/did_you_mean/commit/3f69171813
2020-12-22Sync did_you_meanYuki Nishijima
2020-06-06Remove experimental feaures and related code completelyYuki Nishijima
Original pull request: https://.com/ruby/did_you_mean/pull/147
2020-06-06Sync did_you_meanYuki Nishijima
Notes: Merged: https://.com/ruby/ruby/pull/3135
2020-05-12Revert "Sync did_you_mean"Nobuyoshi Nakada
This reverts commit 946dadd3f479198e87873a863d15c7660a8e2b56, which broke `TestGemRequire` and others.
2020-05-11Sync did_you_meanYuki Nishijima
2019-12-24Sync did_you_meanYuki Nishijima
2019-12-13Drop delegate dependencyYuki Nishijima
Original comment: https://.com/ruby/did_you_mean/commit/2f26c9ee770f28da0942c42cbc9e5800535b75e1
2019-12-05Fix `warning: already initialized constant DidYouMean::VERSION`Kazuhiro NISHIYAMA
``` .../gems/did_you_mean-1.3.1/lib/did_you_mean/version.rb:2: warning: already initialized constant DidYouMean::VERSION .../lib/did_you_mean/version.rb:2: warning: previous definition of VERSION was here ```
2019-12-04Do not attempt to call methods on the receiver if it is a basic objectYuki Nishijima
2019-11-30Promote did_you_mean to default gemKevin Deisz
At the moment, there are some problems with regard to bundler + did_you_mean because of did_you_mean being a bundled gem. Since the vendored version of thor inside bundler and ruby itself explicitly requires did_you_mean, it can become difficult to load it when using Bundler.setup. See this issue: https://.com/yuki24/did_you_mean/issues/117#issuecomment-482733159 for more details. Notes: Merged: https://.com/ruby/ruby/pull/2689
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-24 01:03:28 +0000