Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Enable Style/ParenthesesAroundCondition cop | Ryuta Kamizono | 2018-08-19 | 1 | -2/+2 |
| | | | | To prevent style check in review like https://github.com/rails/rails/pull/33608#discussion_r211087605. | ||||
* | Partly revert #32289 to provide Rails' custom fallback in case | utilum | 2018-05-01 | 1 | -2/+49 |
| | | | | | | | | | | | `DidYouMean::SpellChecker` is not defined. `did_you_mean` is bundled in Ruby but can be uninstalled, and is not always available, sometimes even on our CI: https://travis-ci.org/rails/rails/jobs/372638523#L2405 https://travis-ci.org/rails/rails/jobs/372638523#L2416 https://travis-ci.org/rails/rails/jobs/372638523#L2427 ... | ||||
* | Use `did_you_mean` spell checker for option suggestions | Genadi Samokovarov | 2018-03-23 | 1 | -44/+2 |
| | | | | | | | | | | | Now that we require Ruby over `2.3`, we can replace the current suggestion methods we have with tooling from the `did_you_mean` gem. There is a small user visible change and this is that we now offer a single suggestion for misspelled options. We are suggesting fixes during generator invocation and during a mistyped rails server rack handler. In both cases, if we don't make a proper prediction on the first match, we won't do so in the second or third one, so in my mind, this is okay. | ||||
* | Extract Rails::Command::Spellchecker | Genadi Samokovarov | 2018-03-04 | 1 | -0/+53 |