SirenClient 
A simple client for traversing Siren APIs. Not sure what Siren is? View the spec here: https://github.com/kevinswiber/siren.
Usage
Grabbing the root of the API.
require 'siren_client'
# The simplest form
root = SirenClient.get('http://siren-api.example.com')
# Advanced usage
root = SirenClient.get({
url: 'http://siren-api.example.com',
headers: { "Accept" => "application/json", ... },
basic_auth: { username: 'person', password: '1234' },
timeout: 5,
... # Refer to https://github.com/jnunemaker/httparty/blob/master/lib/httparty.rb#L45
# For more options.
})There are four main parts to an Entity in Siren. (properties, entities, links, and actions) To make your life a little easier SirenClient will try to pick one of the four items given a method name. Otherwise you can access the data directly.
Properties
# If color was a property on the root you could do something like this:
root.color
# or
root.properties['color']Entities
Since entities are usually the most important, SirenClient provides enumerable support to obtain them.
# Will grab the entity as if root was an array.
root[x]
# or
root.entities[x] # This is an array
# Will iterate through all the entities on the root.
root.each do |entity|
# do something
end
# With full enumerable support entities work similarly to arrays
root.map { |entity| ... }
root.select { |entity| ... }
root.find { |entity| ... }
# You can view all the enumerable methods here: http://ruby-doc.org/core-2.0.0/Enumerable.htmlEntities also provide the method .search for searching across sub-entities' classes, rels, and hrefs (sub-links only).
root.search("messages") # => Array<SirenClient::Entity>
root.search(/(messages|concepts)/) # => Array<SirenClient::Entity>Entity sub-links
If the root contains an entity that is an embedded link you can call it based on it's class name. This will also execute the link's href and return you the entity.
root.embedded_link_class_name
root.messages # For exampleLinks
# If you know the link's name you could do something like this:
root.concepts
# or
root.links['concepts'].goActions
# Again, if you know the action's name you can do this:
root.filter_concepts.where(name: 'github', status: 'active')
# or
root.actions['filter_concepts'].where(...)Fields
Actions have fields that are used to make the request when you use .where. To see those fields you can do this:
action = root.actions[0]
action.fields.each do |field|
puts "#Field: {field.name}, #{field.type}, #{field.value}, #{field.title}"
endAccessing the raw response
SirenClient can give you the raw response if needed. Some scenarios where this is useful:
- When the API doesn't return a siren JSON structure.
- Verifying response headers, status code, etc
You can access the raw response with the following examples:
root = SirentClient.get(...)
# For sub-entities i.e. one named `test_concepts`
root.with_raw_response.test_concepts
# For links
root.with_raw_response.concepts
# For actions (this is different from the others)
root.filter_concepts.with_raw_response.where(...)Once you get the raw response instance you can call the following functions:
raw.class == SirenClient::RawResponse
raw.body # Returns the raw body of the response
raw.code # Returns the HTTP status code
raw.message # Returns the HTTP message i.e. "OK"
raw.headers # A hash of the headers in the responseDevelopment
Run the following commands to start development:
bundle install
bundle exec guard
# This will open a CLI that watches files for changes.I've included byebug as a development dependency and you may use it as well.
Thanks To
Kevin Swiber - For creating the Siren spec and giving this project meaning.