aboutsummaryrefslogtreecommitdiffstats
path: root/lib/did_you_mean
Commit message (Collapse)AuthorAgeFilesLines
* [ruby/did_you_mean] Do not suggest #name= for #name and vice versaMatthew Boeh2022-12-051-0/+7
| | | | | | | | | (https://github.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 <jean.boussier+github@shopify.com> Co-authored-by: Jean byroot Boussier <jean.boussier+github@shopify.com>
* [ruby/did_you_mean] Bump version to 1.6.2Hiroshi SHIBATA2022-12-051-1/+1
| | | | https://github.com/ruby/did_you_mean/commit/f5b15128e2
* [ruby/did_you_mean] Fixed correction duplicates in VariableNameCheckerImir Kiyamov2022-09-011-1/+1
| | | | https://github.com/ruby/did_you_mean/commit/c3fc412f6f
* Manually merged https://github.com/ruby/did_you_mean/pull/177Hiroshi SHIBATA2022-06-071-15/+40
|
* [ruby/did_you_mean] Fix `frozen_string_literal is ignored after any tokens` ↵Jean byroot Boussier2022-05-201-1/+2
| | | | | | | | | | warning. (https://github.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://github.com/ruby/did_you_mean/commit/531760f323
* Sync did_you_meanYuki Nishijima2021-12-246-4/+22
|
* Revert the commits for did_you_meanYuki Nishijima2021-12-236-13/+4
| | | | | | This reverts commit feaf4fbc3fa16382fbd07158c448c7b5bdae78b5. This reverts commit 0d4bfbdbe1f880c712b3e60de5fce423e6096f8d. This reverts commit ac4e0978ee4358430396403065eabe1aca05784f.
* * gems/default_gems: Sync did_you_meanYuki Nishijima2021-12-226-4/+13
|
* Revert commits for did_you_meanYuki Nishijima2021-12-216-13/+4
| | | | | | | This reverts commit 4560091b1c99ab33db0d653b9dd2d977fe4676d5. This reverts commit a6f76122a2395bd914daa0aa04fb5a6ce4e0c045. This reverts commit e59b18a6379c55f15ccda85c27d6997d44ef5293. This reverts commit 505dfae05d56d844ea150676edb87850a406d071.
* * gems/default_gems: Sync did_you_meanYuki Nishijima2021-12-216-4/+13
|
* Sync did_you_mean againYuki Nishijima2021-10-226-91/+75
|
* Revert "Sync did_you_mean"Yuki Nishijima2021-10-226-75/+91
| | | | This reverts commit e22d293e06966733e71a7fd9725eee06c03d0177.
* Sync did_you_meanYuki Nishijima2021-10-226-91/+75
|
* Use String#include? instead of end_with? to avoid message duplicationYusuke Endoh2021-06-291-1/+1
| | | | | | | | | | | 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://github.com/ruby/did_you_mean/commit/b35e030549
* Let Correctable#original_message skip prepended method definitionsYusuke Endoh2021-06-291-1/+8
| | | | | | | | | | | | | | | | | 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://github.com/ruby/did_you_mean/commit/8352c154e3
* Should require "rbconfig" to use RbConfigNobuyoshi Nakada2021-06-291-0/+1
| | | | https://github.com/ruby/did_you_mean/commit/fbe5aaaae8
* Start v1.6.0 developmentYuki Nishijima2021-06-291-1/+1
| | | | https://github.com/ruby/did_you_mean/commit/3f69171813
* Sync did_you_meanYuki Nishijima2020-12-221-1/+1
|
* Remove experimental feaures and related code completelyYuki Nishijima2020-06-062-85/+0
| | | | Original pull request: https://github.com/ruby/did_you_mean/pull/147
* Sync did_you_meanYuki Nishijima2020-06-064-115/+116
|
* 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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-09-07 04:27:25 +0000