Ruby bindings to the Clever API. Documentation
Add this line to your application's Gemfile:
gem 'clever-ruby'
And then execute:
$ bundle
Or install it yourself as:
$ gem install clever-ruby
Configure clever-ruby to use your Clever token:
Clever.configure do |config|
config.token = 'YOUR-API-TOKEN'
end
See the documentation for further details.
To run all tests:
$ rake test
To run a specific test file, for example test/unit/clever_test.rb
:
$ rake test TEST=test/unit/clever_test.rb
To run all tests and the linter (rubocop):
$ rake
The linter follows the Ruby Style Guide with a few exceptions. To just run the linter:
$ rake lint
It is not currently possible to easily recreate the scenario in which the original VCR cassettes were recorded, especially for the events. If you need to update or add to the recorded requests and responses:
- Using a Clever District Admin sandbox account, set up the data to include the updated or added situation.
- In the tests, temporarily replace
DEMO_TOKEN
with the OAuth token of your sandbox district. - Remove the existing VCR cassettes that you would like to update so that they will get rerecorded.
- Run the tests.
- Using a combination of
git checkout -p
,git add -p
, find-and-replace,sed
/awk
, etc. check into git the updated data and any updated formatting that you want to keep. Check out and discard any recordings of yourBearer Token
(so that the cassettes all containDEMO_TOKEN
) and any other irrelevant data changes. Change the IDs of any objects in your added or updated response data to match those of the demo data.
To generate it to ./doc
:
$ rake doc
To see documentation coverage:
$ rake doc-coverage
and then view doc_coverage.txt
.
- Fork it
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git add -p ./path/to/files; git commit -m 'Add some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create new Pull Request