Brian Bugh
Brian Bugh
You can work around this by explicitly including `rspec` in your `Gemfile`, along with `rspec-rails`. ```ruby gem 'rspec' gem 'rspec-rails' ```
I had just come to the repo to check if this cop was being worked on already so I could submit it. Thank you for doing this!
Not sure if this is helpful more than a year later, but in case anyone else comes across this, you can do math in in Rantly blocks on the property...
I had this problem as well and ended up here from some searching. I was able to "solve" (hack) the problem using BetterTouchTool and using an Accessibility Keyboard Panel to...
Rather than "rounding" being a boolean, it would be preferable if it was to a specific precision, with a default of 0 ``` toHslString({ precision: 2 }) ``` because for...
FYI it appears that 0.11.0 is looking for wasm-opt in the wrong path. A few minutes ago the build was working, I just upgraded wasm-pack, and now there's an error...
`master` branch appears to be working. I deleted the symbolic link with `/bin/bin` to be sure. ``` rm -rf /opt/homebrew/bin/bin/wasm-opt cd /tmp git clone https://github.com/rustwasm/wasm-pack cd wasm-pack cargo build --release...
A fix for this was already accepted in PR #84, we just need a new release to resolve the issue. @MaxLeiter what do you think about doing a point release...
@joeldenning would you accept a PR for this?
Correct. Engines have both a `Gemfile` and an `engine_name.gemspec` file. The officially recommended way to load gems is to use the .gemspec, as we would with any gem. We have...