grape-entity 0.4.0 → 0.4.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 35f4a45cc741d725e9cc8d180ae9db0f9123cb7a
-  data.tar.gz: a452232a49b72773f38710733c24104e113e7043
+  metadata.gz: effe94d496aff5e6a72b380ddaac6daa7a12b07d
+  data.tar.gz: 324af303ff5358862861de75be31cb3b0d5d5eab
 SHA512:
-  metadata.gz: aeaab5ee1c623a0f4359a4b5378b3536afefd0a23009007a5c0a91fb4086658da6abd53458ea85bcd724dea448b0598213160bf74b58084e4ee68a840e0df511
-  data.tar.gz: 6f187c4bb82bea91a739fb3dc8c48d04985b3b72d09e29e91e6565b42ceecb281275d3c973eb3062b25263a997955dcece3efa7fe297ca1dd1e209e7b18dc3ea
+  metadata.gz: 53357805d3b83631c727a22ce88d81ecb1fdba53a225a063bb67a68d711ac8c86ea67d6297938f4d2192dbf00f591833aff7f00e0af60b8ca984292840e09c9c
+  data.tar.gz: 02d43ad57fb18f7eb9b3927a346f447233fd42d6f73f0591a296c8f0378a5dc16c7ff8cbe53c606c6720b9040894ea917e530618c7738814d87f5ccb5ef30f1f

data/CHANGELOG.md

@@ -1,5 +1,11 @@
-Next Release
-============
+0.4.1 (2014-02-13)
+==================
+
+* [#54](https://github.com/intridea/grape-entity/issues/54): Fix: undefined method `to_set` - [@aj0strow](https://github.com/aj0strow).
+
+0.4.0 (2014-01-27)
+==================
+
 * Ruby 1.8.x is no longer supported - [@dblock](https://github.com/dblock).
 * [#36](https://github.com/intridea/grape-entity/pull/36): Enforcing Ruby style guidelines via Rubocop - [@dblock](https://github.com/dblock).
 * [#7](https://github.com/intridea/grape-entity/issues/7): Added `serializable` option to `represent` - [@mbleigh](https://github.com/mbleigh).
@@ -14,7 +20,6 @@ Next Release
 * [#46](https://github.com/intridea/grape-entity/issues/46), [#50](https://github.com/intridea/grape-entity/pull/50): Added support for specifying the presenter class in `using` in string format - [@larryzhao](https://github.com/larryzhao).
 * [#51](https://github.com/intridea/grape-entity/pull/51): Raise `ArgumentError` if an unknown option is used with `expose` - [@aj0strow](https://github.com/aj0strow).
 * [#51](https://github.com/intridea/grape-entity/pull/51): Alias `:with` to `:using`, consistently with the Grape api endpoints - [@aj0strow](https://github.com/aj0strow).
-* Your contribution here.
 
 0.3.0 (2013-03-29)
 ==================

data/CONTRIBUTING.md

@@ -0,0 +1,118 @@
+Contributing to Grape-Entity
+============================
+
+Grape-Entity is work of [many of contributors](https://github.com/intridea/grape-entity/graphs/contributors). You're encouraged to submit [pull requests](https://github.com/intridea/grape-entity/pulls), [propose features and discuss issues](https://github.com/intridea/grape-entity/issues). When in doubt, ask a question in the [Grape Google Group](http://groups.google.com/group/ruby-grape).
+
+#### Fork the Project
+
+Fork the [project on Github](https://github.com/intridea/grape-entity) and check out your copy.
+
+```
+git clone https://github.com/contributor/grape-entity.git
+cd grape-entity
+git remote add upstream https://github.com/intridea/grape-entity.git
+```
+
+#### Create a Topic Branch
+
+Make sure your fork is up-to-date and create a topic branch for your feature or bug fix.
+
+```
+git checkout master
+git pull upstream master
+git checkout -b my-feature-branch
+```
+
+#### Bundle Install and Test
+
+Ensure that you can build the project and run tests.
+
+```
+bundle install
+bundle exec rake
+```
+
+#### Write Tests
+
+Try to write a test that reproduces the problem you're trying to fix or describes a feature that you want to build. Add to [spec/grape-entity](spec/grape-entity).
+
+We definitely appreciate pull requests that highlight or reproduce a problem, even without a fix.
+
+#### Write Code
+
+Implement your feature or bug fix.
+
+Ruby style is enforced with [Rubocop](https://github.com/bbatsov/rubocop), run `bundle exec rubocop` and fix any style issues highlighted.
+
+Make sure that `bundle exec rake` completes without errors.
+
+#### Write Documentation
+
+Document any external behavior in the [README](README.md).
+
+#### Update Changelog
+
+Add a line to [CHANGELOG](CHANGELOG.md) under *Next Release*. Make it look like every other line, including your name and link to your Github account.
+
+#### Commit Changes
+
+Make sure git knows your name and email address:
+
+```
+git config --global user.name "Your Name"
+git config --global user.email "contributor@example.com"
+```
+
+Writing good commit logs is important. A commit log should describe what changed and why.
+
+```
+git add ...
+git commit
+```
+
+#### Push
+
+```
+git push origin my-feature-branch
+```
+
+#### Make a Pull Request
+
+Go to https://github.com/contributor/grape-entity and select your feature branch. Click the 'Pull Request' button and fill out the form. Pull requests are usually reviewed within a few days.
+
+#### Rebase
+
+If you've been working on a change for a while, rebase with upstream/master.
+
+```
+git fetch upstream
+git rebase upstream/master
+git push origin my-feature-branch -f
+```
+
+#### Update CHANGELOG Again
+
+Update the [CHANGELOG](CHANGELOG.md) with the pull request number. A typical entry looks as follows.
+
+```
+* [#123](https://github.com/intridea/grape-entity/pull/123): Reticulated splines - [@contributor](https://github.com/contributor).
+```
+
+Amend your previous commit and force push the changes.
+
+```
+git commit --amend
+git push origin my-feature-branch -f
+```
+
+#### Check on Your Pull Request
+
+Go back to your pull request after a few minutes and see whether it passed muster with Travis-CI. Everything should look green, otherwise fix issues and amend your commit as described above.
+
+#### Be Patient
+
+It's likely that your change will not be merged and that the nitpicky maintainers will ask you to do more, or fix seemingly benign problems. Hang on there!
+
+#### Thank You
+
+Please do know that we really appreciate and value your time and work. We love you, really.

data/RELEASING.md

@@ -0,0 +1,82 @@
+Releasing Grape-Entity
+======================
+
+There're no particular rules about when to release grape-entity. Release bug fixes frequenty, features not so frequently and breaking API changes rarely.
+
+### Release
+
+Run tests, check that all tests succeed locally.
+
+```
+bundle install
+rake
+```
+
+Check that the last build succeeded in [Travis CI](https://travis-ci.org/intridea/grape-entity) for all supported platforms.
+
+Increment the version, modify [lib/grape-entity/version.rb](lib/grape-entity/version.rb).
+
+*  Increment the third number if the release has bug fixes and/or very minor features, only (eg. change `0.5.1` to `0.5.2`).
+*  Increment the second number if the release contains major features or breaking API changes (eg. change `0.5.1` to `0.4.0`).
+
+Change "Next Release" in [CHANGELOG.md](CHANGELOG.md) to the new version.
+
+```
+0.4.0 (2014-01-27)
+==================
+```
+
+Remove the line with "Your contribution here.", since there will be no more contributions to this release.
+
+Commit your changes.
+
+```
+git add README.md CHANGELOG.md lib/grape-entity/version.rb
+git commit -m "Preparing for release, 0.4.0."
+git push origin master
+```
+
+Release.
+
+```
+$ rake release
+
+grape-entity 0.4.0 built to pkg/grape-entity-0.4.0.gem.
+Tagged v0.4.0.
+Pushed git commits and tags.
+Pushed grape-entity 0.4.0 to rubygems.org.
+```
+
+### Prepare for the Next Version
+
+Add the next release to [CHANGELOG.md](CHANGELOG.md).
+
+```
+Next Release
+============
+
+* Your contribution here.
+```
+
+Comit your changes.
+
+```
+git add CHANGELOG.md README.md
+git commit -m "Preparing for next release."
+git push origin master
+```
+
+### Make an Announcement
+
+Make an announcement on the [ruby-grape@googlegroups.com](mailto:ruby-grape@googlegroups.com) mailing list. The general format is as follows.
+
+```
+Grape-entity 0.4.0 has been released.
+
+There were 8 contributors to this release, not counting documentation.
+
+Please note the breaking API change in ...
+
+[copy/paste CHANGELOG here]
+
+```

data/Rakefile

@@ -15,6 +15,7 @@ RSpec::Core::RakeTask.new(:rcov) do |spec|
 end
 
 task :spec
+require 'rainbow/ext/string' unless String.respond_to?(:color)
 require 'rubocop/rake_task'
 Rubocop::RakeTask.new(:rubocop)
 

data/lib/grape_entity/entity.rb

@@ -1,4 +1,5 @@
 require 'multi_json'
+require 'set'
 
 module Grape
   # An Entity is a lightweight structure that allows you to easily

data/lib/grape_entity/version.rb

@@ -1,3 +1,3 @@
 module GrapeEntity
-  VERSION = '0.4.0'
+  VERSION = '0.4.1'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: grape-entity
 version: !ruby/object:Gem::Version
-  version: 0.4.0
+  version: 0.4.1
 platform: ruby
 authors:
 - Michael Bleigh
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-01-27 00:00:00.000000000 Z
+date: 2014-02-13 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -122,10 +122,12 @@ files:
 - .travis.yml
 - .yardopts
 - CHANGELOG.md
+- CONTRIBUTING.md
 - Gemfile
 - Guardfile
 - LICENSE
 - README.md
+- RELEASING.md
 - Rakefile
 - grape-entity.gemspec
 - lib/grape-entity.rb
@@ -154,9 +156,11 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: grape-entity
-rubygems_version: 2.0.3
+rubygems_version: 2.0.14
 signing_key: 
 specification_version: 4
 summary: A simple facade for managing the relationship between your model and API.
-test_files: []
+test_files:
+- spec/grape_entity/entity_spec.rb
+- spec/spec_helper.rb
 has_rdoc: