I'm hoping we don't actually need it because we explicitly enable
fractional seconds precision in our `dummy_app` migration by
specifying `limit(6)`.
Works on my machine, but I use mariadb. We'll see how well it works
on TravisCI, which runs mysql 5.6.33.
MySQL added support for `limit(6)` in 5.6.4, so I'm hopeful.
- Fix Lint/RescueWithoutErrorClass
- And I use the term "fix" loosely
- Fix RSpec/PredicateMatcher
- The failure message should actually be better this way too.
- RSpec/LetBeforeExamples
- RSpec/HookArgument
- Fix RSpec/ExpectInHook in widget_spec.rb
- Fix RSpec/MessageSpies
- I like spies. I've never linted them before, but I like how they
separate test setup from assertions.
- Convert serializers/mixin_json_test.rb to rspec
- Convert functional/thread_safety_test.rb to rspec
- Convert functional/controller_test.rb to rspec
- Move the dummy app from test to spec, delete test dir
The reason some projects have both is so that some spec files can be
run in isolation, without the rails stuff. In practice, I don't find
myself ever doing this. So, the complexity of two files is unnecessary.
pry-nav works, but produces a "circular require" warning.
The warning was fixed in 2016, but no new version of pry-nav
has been released.
https://github.com/nixme/pry-nav/pull/26
In fact, the pry-nav readme recommends using pry-byebug.
Jared Beck