The project is in a healthy, maintained state
Code style checking for CableReady
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
 Dependencies

Development

>= 0

Runtime

~> 1.0
>= 1.1.0
 Project Readme

RuboCop::CableReady

CableReady-specific analysis for your projects, as an extension to RuboCop.

Installation

Add this line to your application's Gemfile:

gem 'rubocop-cable_ready'

And then execute:

bundle install

Or install it yourself as:

gem install rubocop-cable_ready

Usage

You need to tell RuboCop to load the CableReady extension. There are threeways to do this:

RuboCop configuration file

Put this into your .rubocop.yml.

require: rubocop-cable_ready

Alternatively, use the following array notation when specifying multiple extensions.

require:
  - rubocop-other-extension
  - rubocop-cable_ready

Now you can run rubocop and it will automatically load the RuboCop CableReady cops together with the standard cops.

Command line

rubocop --require rubocop-cable_ready

Rake task

RuboCop::RakeTask.new do |task|
  task.requires << 'rubocop-cable_ready'
end

Development

After checking out the repo, run bin/setup to install dependencies. Then, run rake test to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and the created tag, and push the .gem file to rubygems.org.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/marcoroth/rubocop-cable_ready. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.

License

The gem is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the RuboCop::CableReady project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.