Provides a Ruby interface to Context.IO. The general design was inspired by the wonderful aws-sdk gem. You start with an object that represents your account with Context.IO and then you deal with collections within that going forward. Check out the example.
If you're looking at the Context.IO docs, it is important to note that there are
some attributes that've been renamed to be a bit more Ruby-friendly. In general,
if the API returns a number meant to be seconds-from-epoch, then it's been
converted to return a Time (e.g. updated has changed to updated_at) and a
boolean has converted to something with a ? at the end (e.g. HasChildren and
initial_import_finished are has_children? and initial_import_finished?,
respectively).
require 'contextio'
contextio = ContextIO.new('your_api_key', 'your_api_secret')
account = contextio.accounts.where(email: '[email protected]').first
account.email_addresses # ['[email protected]', '[email protected]']
account.first_name # 'Bruno'
account.suspended? # False
account.messages.where(folder: '\Drafts').each do |m|
puts m.subject
endTo grab some object you already know the primary key for, you'll use the []
method like you would for a Hash or Array. This is most helpful for
accounts, but works for any resource collection.
require 'contextio'
contextio = ContextIO.new('your_api_key', 'your_api_secret')
account = contextio.accounts[some_account_id]
email_Address = account.messages[some_message_id]$ gem install contextio
Or, of course, put this in your Gemfile:
gem contextio
This gem adheres to SemVer. So you should be pretty safe upgrading from 1.0.0 to 1.9.9. Whatever as long as the major version doesn't bump. When the major version bumps, be warned; upgrading will take some kind of effort.
Help is gladly welcomed. If you have a feature you'd like to add, it's much more likely to get in (or get in faster) the closer you stick to these steps:
- Open an Issue to talk about it. We can discuss whether it's the right direction or maybe help track down a bug, etc.
- Fork the project, and make a branch to work on your feature/fix. Master is where you'll want to start from.
- Turn the Issue into a Pull Request. There are several ways to do this, but hub is probably the easiest.
- Make sure your Pull Request includes tests.
If you don't know how to fix something, even just a Pull Request that includes a failing test can be helpful. If in doubt, make an Issue to discuss.
Copyright (c) 2012 Context.IO
See LICENSE.md for details.