Skip to content
<open-source>
Oeiuwq Faith Blog OpenSource Porfolio

pauldix/sax-machine

A declarative sax parsing library backed by Nokogiri.
Source code at GitHub https://github.com/pauldix/sax-machine
pauldix/sax-machine.json
{
  "createdAt": "2008-12-30T03:11:38Z",
  "defaultBranch": "master",
  "description": "A declarative sax parsing library backed by Nokogiri.",
  "fullName": "pauldix/sax-machine",
  "homepage": "",
  "language": "Ruby",
  "name": "sax-machine",
  "pushedAt": "2021-01-05T00:47:54Z",
  "stargazersCount": 235,
  "topics": [],
  "updatedAt": "2024-02-15T22:40:01Z",
  "url": "https://github.com/pauldix/sax-machine"
}

SAX Machine

Section titled “SAX Machine”

Status

Section titled “Status”

Gem Version Build Status Coverage Status Code Climate Dependencies

Description

Section titled “Description”

A declarative SAX parsing library backed by Nokogiri, Ox or Oga.

Installation

Section titled “Installation”

Add this line to your application’s Gemfile:

gem 'sax-machine'

And then execute:

Terminal window
$ bundle

Usage

Section titled “Usage”

SAX Machine can use either nokogiri, ox or oga as XML SAX handler.

To use Nokogiri add this line to your Gemfile:

gem 'nokogiri', '~> 1.6'

To use Ox add this line to your Gemfile:

gem 'ox', '>= 2.1.2'

To use Oga add this line to your Gemfile:

gem 'oga', '>= 0.2.0'

You can also specify which handler to use manually, like this:

SAXMachine.handler = :nokogiri

Examples

Section titled “Examples”

Include SAXMachine in any class and define properties to parse:

class AtomContent
  include SAXMachine
  attribute :type
  value :text
end


class AtomEntry
  include SAXMachine
  element :title
  # The :as argument makes this available through entry.author instead of .name
  element :name, as: :author
  element "feedburner:origLink", as: :url
  # The :default argument specifies default value for element when it's missing
  element :summary, class: String, default: "No summary available"
  element :content, class: AtomContent
  element :published
  ancestor :ancestor
end


class Atom
  include SAXMachine
  # Use block to modify the returned value
  # Blocks are working with pretty much everything,
  # except for `elements` with `class` attribute
  element :title do |title|
    title.strip
  end
  # The :with argument means that you only match a link tag
  # that has an attribute of type: "text/html"
  element :link, value: :href, as: :url, with: {
    type: "text/html"
  }
  # The :value argument means that instead of setting the value
  # to the text between the tag, it sets it to the attribute value of :href
  element :link, value: :href, as: :feed_url, with: {
    type: "application/atom+xml"
  }
  elements :entry, as: :entries, class: AtomEntry
end

Then parse any XML with your class:

feed = Atom.parse(xml_text)


feed.title # Whatever the title of the blog is
feed.url # The main URL of the blog
feed.feed_url # The URL of the blog feed


feed.entries.first.title # Title of the first entry
feed.entries.first.author # The author of the first entry
feed.entries.first.url # Permalink on the blog for this entry
feed.entries.first.summary # Returns "No summary available" if summary is missing
feed.entries.first.ancestor # The Atom ancestor
feed.entries.first.content # Instance of AtomContent
feed.entries.first.content.text # Entry content text

You can also use the elements method without specifying a class:

class ServiceResponse
  include SAXMachine
  elements :message, as: :messages
end


response = ServiceResponse.parse("
  <response>
    <message>hi</message>
    <message>world</message>
  </response>
")
response.messages.first # hi
response.messages.last  # world

To limit conflicts in the class used for mappping, you can use the alternate SAXMachine.configure syntax:

class X < ActiveRecord::Base
  # This way no element, elements or ancestor method will be added to X
  SAXMachine.configure(X) do |c|
    c.element :title
  end
end

Multiple elements can be mapped to the same alias:

class RSSEntry
  include SAXMachine
  # ...
  element :pubDate, as: :published
  element :pubdate, as: :published
  element :"dc:date", as: :published
  element :"dc:Date", as: :published
  element :"dcterms:created", as: :published
end

If more than one of these elements exists in the source, the value from the last one is used. The order of the element declarations in the code is unimportant. The order they are encountered while parsing the document determines the value assigned to the alias.

If an element is defined in the source but is blank (e.g., <pubDate></pubDate>), it is ignored, and non-empty one is picked.

Contributing

Section titled “Contributing”
  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

LICENSE

Section titled “LICENSE”

The MIT License

Copyright (c) 2009-2014:

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ‘Software’), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED ‘AS IS’, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.