summaryrefslogtreecommitdiff
path: root/lib/did_you_mean
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Sync did_you_mean"Nobuyoshi Nakada2020-05-122-39/+1
| | | | | This reverts commit 946dadd3f479198e87873a863d15c7660a8e2b56, which broke `TestGemRequire` and others.
* Sync did_you_meanYuki Nishijima2020-05-112-1/+39
|
* Sync did_you_meanYuki Nishijima2019-12-241-1/+1
|
* Drop delegate dependencyYuki Nishijima2019-12-131-4/+3
| | | | | Original comment: https://github.com/ruby/did_you_mean/commit/2f26c9ee770f28da0942c42cbc9e5800535b75e1
* Fix `warning: already initialized constant DidYouMean::VERSION`Kazuhiro NISHIYAMA2019-12-051-1/+5
| | | | | | | ``` .../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 ```
* Do not attempt to call methods on the receiver if it is a basic objectYuki Nishijima2019-12-041-5/+13
|
* Promote did_you_mean to default gemKevin Deisz2019-11-3019-0/+796
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://github.com/yuki24/did_you_mean/issues/117#issuecomment-482733159 for more details.