Project

opushon

0.0
No commit activity in last 3 years
No release in over 3 years
An Opushon's body parser and emitter.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 2.0
~> 12.3
~> 0.74
~> 0.17
~> 3.0
 Project Readme

Opushon

Build Status Gem Version Inline docs

An Opushon's body parser and emitter.

Contact

Rubies

Installation

Add this line to your application's Gemfile:

gem 'opushon'

And then execute:

$ bundle

Or install it yourself as:

$ gem install opushon

Usage

# Parse some Opushon
opushon = Opushon.load('{
            "DELETE": {
              "title": "Delete issues",
              "description": "Remove every issues.",
              "request": {
                "headers": {},
                "query_string": {},
                "body": {}
              },
              "response": {
                "headers": {},
                "query_string": {},
                "body": {}
              }
            }
          }') # => an Opushon instance

# Emit some Opushon
Opushon.dump(opushon) # => "{\"GET\":null,\"PATCH\":null,\"PUT\":null,\"POST\":null,\"DELETE\":{\"title\":\"Delete issues\",\"description\":\"Remove every issues.\",\"request\":{\"headers\":{},\"query_string\":{},\"body\":{}},\"response\":{\"headers\":{},\"body\":{}}}}"

Security

As a basic form of security Opushon provides a set of SHA512 checksums for every Gem release. These checksums can be found in the checksum/ directory. Although these checksums do not prevent malicious users from tampering with a built Gem they can be used for basic integrity verification purposes.

The checksum of a file can be checked using the sha512sum command. For example:

$ sha512sum pkg/opushon-0.2.gem
17173a517daa21256cc2391ba275f6977086ecda0e6f750fbb380ad08430bb748d5cdc927b8e904850b15fe47a121985dafa74a6b15df46100b86decf40c8cda  pkg/opushon-0.2.gem

Versioning

Opushon follows Semantic Versioning 2.0.

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 a new Pull Request

License

See LICENSE.md file.