RubyGems - acts_as_api - Versions diffs - 1.0.0 → 1.0.1 - Mend

acts_as_api 1.0.0 → 1.0.1

Files changed (11) hide show

checksums.yaml +4 -4
data/History.txt +6 -2
data/README.md +1 -1
data/docs/index.html +5 -5
data/docs/index.rb +4 -4
data/lib/acts_as_api/version.rb +1 -1
data/spec/shared_engine/shared_engine.gemspec +1 -1
metadata +3 -9
data/spec/active_record_dummy/README.rdoc +0 -261
data/spec/shared_engine/MIT-LICENSE +0 -20
data/spec/shared_engine/README.rdoc +0 -3

checksums.yaml CHANGED

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: e16fbb94ed887cceb26f045b1249335016a07682
-  data.tar.gz: 40ad8d4be72657344be7ad856eb7c83b66dcf389
+  metadata.gz: 7f15149b411afbf4fa0bac53a8ddaf1491d2411c
+  data.tar.gz: 1d36f9afd8b51721a6be06a0b0e8cc0b523d192e
 SHA512:
-  metadata.gz: d08be30be0f420cd61e61bb3da1e98b798d420e8c6a8be3afadafa1e897c0c3180f734a2c374baa711afbd07b56b09503fa3dd25eaf041622aa5b119cfbf8917
-  data.tar.gz: 68debff236e8e0e78203841aa33c253949b36dfb518c3d5f75f9ad5bc7002ec01090c80dc0b441e57d363b6c141b36d1d2b1adaa60cb226c7900f3683c5383ed
+  metadata.gz: ae768bfd57b425098259630ad8ed0a0bc093c6f9e3854545bbc8fa03dcfc048772d59b2ed4498e8ded32b2d8a701b6571bfe74fbd18e31cf074e0c3158e4f438
+  data.tar.gz: efc12084e514fa4520d2e1773a32a535c8cc33f1d50d8a07cf942d47dd16a5c7cf650177c8ad6cbdf010474ccaaadd7a76bac351403cccc6e11b727a636e1a08

data/History.txt CHANGED

@@ -1,3 +1,7 @@
+=== 1.0.1 2017-08-04
+* Updates spec suite to Rails 5.1.3
 === 1.0.0 2016-11-24
 * Ditch Ruby 1.8 syntax, overall modernization
@@ -59,13 +63,13 @@
 === 0.3.2 2011-04-20
-* Raise an exception if a specified api template is not found
+* Raise an exception if a specified api template is not found
 === 0.3.1 2011-04-08
 * Added the :template option to specify sub templates
-* Fixed a bug concerning extended api templates
+* Fixed a bug concerning extended api templates
 === 0.3.0 2011-02-22

data/README.md CHANGED

@@ -23,7 +23,7 @@ class User < ActiveRecord::Base
   end
   # will render json: { "user": { "first_name": "John", "age":  26 } }
-  api_accessible :private, :extend => :public do |template|
+  api_accessible :private, extend: :public do |template|
     template.add :last_name
     template.add :email
   end

data/docs/index.html CHANGED

@@ -3,7 +3,7 @@
 <head>
   <meta http-equiv="content-type" content="text/html;charset=utf-8">
   <title>acts_as_api</title>
-  <meta content="A Ruby/Rails gem to easily generate web api reponses!" name="description" />
+  <meta content="A Ruby/Rails gem to easily generate web api responses!" name="description" />
   <meta content="Christian Bäuerlein" name="author" />
   <meta content="en" name="language" />
   <link rel="stylesheet" href="./docco.css">
@@ -202,8 +202,8 @@ If you only want to expose the <code>first_name</code> and <code>last_name</code
       </td>
       <td class=code>
         <div class='highlight'><pre>    <span class="n">respond_to</span> <span class="k">do</span> <span class="o">|</span><span class="nb">format</span><span class="o">|</span>
-      <span class="nb">format</span><span class="o">.</span><span class="n">xml</span>  <span class="p">{</span> <span class="n">render_for_api</span> <span class="ss">:name_only</span><span class="p">,</span> <span class="ss">:xml</span> <span class="o">=&gt;</span> <span class="vi">@users</span><span class="p">,</span> <span class="ss">:root</span> <span class="o">=&gt;</span> <span class="ss">:users</span>  <span class="p">}</span>
-      <span class="nb">format</span><span class="o">.</span><span class="n">json</span> <span class="p">{</span> <span class="n">render_for_api</span> <span class="ss">:name_only</span><span class="p">,</span> <span class="ss">:json</span> <span class="o">=&gt;</span> <span class="vi">@users</span><span class="p">,</span> <span class="ss">:root</span> <span class="o">=&gt;</span> <span class="ss">:users</span> <span class="p">}</span>
+      <span class="nb">format</span><span class="o">.</span><span class="n">xml</span>  <span class="p">{</span> <span class="n">render_for_api</span> <span class="ss">:name_only</span><span class="p">,</span> <span class="ss">xml</span><span class="p">:</span> <span class="vi">@users</span><span class="p">,</span>  <span class="ss">root</span><span class="p">:</span> <span class="ss">:users</span> <span class="p">}</span>
+      <span class="nb">format</span><span class="o">.</span><span class="n">json</span> <span class="p">{</span> <span class="n">render_for_api</span> <span class="ss">:name_only</span><span class="p">,</span> <span class="ss">json</span><span class="p">:</span> <span class="vi">@users</span><span class="p">,</span> <span class="ss">root</span><span class="p">:</span> <span class="ss">:users</span> <span class="p">}</span>
     <span class="k">end</span>
   <span class="k">end</span>
@@ -211,8 +211,8 @@ If you only want to expose the <code>first_name</code> and <code>last_name</code
     <span class="vi">@user</span> <span class="o">=</span> <span class="no">User</span><span class="o">.</span><span class="n">find</span><span class="p">(</span><span class="n">params</span><span class="o">[</span><span class="ss">:id</span><span class="o">]</span><span class="p">)</span>
     <span class="n">respond_to</span> <span class="k">do</span> <span class="o">|</span><span class="nb">format</span><span class="o">|</span>
-      <span class="nb">format</span><span class="o">.</span><span class="n">xml</span>  <span class="p">{</span> <span class="n">render_for_api</span> <span class="ss">:name_only</span><span class="p">,</span> <span class="ss">:xml</span>  <span class="o">=&gt;</span> <span class="vi">@user</span> <span class="p">}</span>
-      <span class="nb">format</span><span class="o">.</span><span class="n">json</span> <span class="p">{</span> <span class="n">render_for_api</span> <span class="ss">:name_only</span><span class="p">,</span> <span class="ss">:json</span> <span class="o">=&gt;</span> <span class="vi">@user</span> <span class="p">}</span>
+      <span class="nb">format</span><span class="o">.</span><span class="n">xml</span>  <span class="p">{</span> <span class="n">render_for_api</span> <span class="ss">:name_only</span><span class="p">,</span> <span class="ss">xml</span><span class="p">:</span> <span class="vi">@user</span>  <span class="p">}</span>
+      <span class="nb">format</span><span class="o">.</span><span class="n">json</span> <span class="p">{</span> <span class="n">render_for_api</span> <span class="ss">:name_only</span><span class="p">,</span> <span class="ss">json</span><span class="p">:</span> <span class="vi">@user</span> <span class="p">}</span>
     <span class="k">end</span>
   <span class="k">end</span>

data/docs/index.rb CHANGED

@@ -62,8 +62,8 @@ class UsersController < ApplicationController
     @users = User.all
     # Note that it's wise to add a `root` param when rendering lists.
     respond_to do |format|
-      format.xml  { render_for_api :name_only, :xml => @users, :root => :users  }
-      format.json { render_for_api :name_only, :json => @users, :root => :users }
+      format.xml  { render_for_api :name_only, xml: @users,  root: :users }
+      format.json { render_for_api :name_only, json: @users, root: :users }
     end
   end
@@ -71,8 +71,8 @@ class UsersController < ApplicationController
     @user = User.find(params[:id])
     respond_to do |format|
-      format.xml  { render_for_api :name_only, :xml  => @user }
-      format.json { render_for_api :name_only, :json => @user }
+      format.xml  { render_for_api :name_only, xml: @user  }
+      format.json { render_for_api :name_only, json: @user }
     end
   end

data/lib/acts_as_api/version.rb CHANGED

@@ -1,3 +1,3 @@
 module ActsAsApi
-  VERSION = '1.0.0'.freeze
+  VERSION = '1.0.1'.freeze
 end

data/spec/shared_engine/shared_engine.gemspec CHANGED

@@ -14,6 +14,6 @@ Gem::Specification.new do |s|
   s.files = Dir['{app,config,db,lib}/**/*'] + ['MIT-LICENSE', 'Rakefile', 'README.rdoc']
-  s.add_dependency 'rails', '~> 5.0.0.1'
+  s.add_dependency 'rails', '~> 5.1.3'
   s.add_development_dependency 'sqlite3'
 end

metadata CHANGED

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: acts_as_api
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - Christian Bäuerlein
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2016-11-24 00:00:00.000000000 Z
+date: 2017-08-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activemodel
@@ -129,7 +129,6 @@ files:
 - spec/README.md
 - spec/active_record_dummy/.gitignore
 - spec/active_record_dummy/Gemfile
-- spec/active_record_dummy/README.rdoc
 - spec/active_record_dummy/Rakefile
 - spec/active_record_dummy/app/models/.gitkeep
 - spec/active_record_dummy/app/models/profile.rb
@@ -193,8 +192,6 @@ files:
 - spec/mongoid_dummy/script/rails
 - spec/shared_engine/.gitignore
 - spec/shared_engine/Gemfile
-- spec/shared_engine/MIT-LICENSE
-- spec/shared_engine/README.rdoc
 - spec/shared_engine/Rakefile
 - spec/shared_engine/app/controllers/shared_engine/application_controller.rb
 - spec/shared_engine/app/controllers/shared_engine/plain_objects_controller.rb
@@ -249,7 +246,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project:
-rubygems_version: 2.6.8
+rubygems_version: 2.6.11
 signing_key:
 specification_version: 4
 summary: Makes creating XML/JSON responses in Rails 3, 4 and 5 easy and fun.
@@ -257,7 +254,6 @@ test_files:
 - spec/README.md
 - spec/active_record_dummy/.gitignore
 - spec/active_record_dummy/Gemfile
-- spec/active_record_dummy/README.rdoc
 - spec/active_record_dummy/Rakefile
 - spec/active_record_dummy/app/models/.gitkeep
 - spec/active_record_dummy/app/models/profile.rb
@@ -321,8 +317,6 @@ test_files:
 - spec/mongoid_dummy/script/rails
 - spec/shared_engine/.gitignore
 - spec/shared_engine/Gemfile
-- spec/shared_engine/MIT-LICENSE
-- spec/shared_engine/README.rdoc
 - spec/shared_engine/Rakefile
 - spec/shared_engine/app/controllers/shared_engine/application_controller.rb
 - spec/shared_engine/app/controllers/shared_engine/plain_objects_controller.rb

data/spec/active_record_dummy/README.rdoc DELETED

@@ -1,261 +0,0 @@
-== Welcome to Rails
-Rails is a web-application framework that includes everything needed to create
-database-backed web applications according to the Model-View-Control pattern.
-This pattern splits the view (also called the presentation) into "dumb"
-templates that are primarily responsible for inserting pre-built data in between
-HTML tags. The model contains the "smart" domain objects (such as Account,
-Product, Person, Post) that holds all the business logic and knows how to
-persist themselves to a database. The controller handles the incoming requests
-(such as Save New Account, Update Product, Show Post) by manipulating the model
-and directing data to the view.
-In Rails, the model is handled by what's called an object-relational mapping
-layer entitled Active Record. This layer allows you to present the data from
-database rows as objects and embellish these data objects with business logic
-methods. You can read more about Active Record in
-link:files/vendor/rails/activerecord/README.html.
-The controller and view are handled by the Action Pack, which handles both
-layers by its two parts: Action View and Action Controller. These two layers
-are bundled in a single package due to their heavy interdependence. This is
-unlike the relationship between the Active Record and Action Pack that is much
-more separate. Each of these packages can be used independently outside of
-Rails. You can read more about Action Pack in
-link:files/vendor/rails/actionpack/README.html.
-== Getting Started
-1. At the command prompt, create a new Rails application:
-       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
-2. Change directory to <tt>myapp</tt> and start the web server:
-       <tt>cd myapp; rails server</tt> (run with --help for options)
-3. Go to http://localhost:3000/ and you'll see:
-       "Welcome aboard: You're riding Ruby on Rails!"
-4. Follow the guidelines to start developing your application. You can find
-the following resources handy:
-* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
-* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
-== Debugging Rails
-Sometimes your application goes wrong. Fortunately there are a lot of tools that
-will help you debug it and get it back on the rails.
-First area to check is the application log files. Have "tail -f" commands
-running on the server.log and development.log. Rails will automatically display
-debugging and runtime information to these files. Debugging info will also be
-shown in the browser on requests from 127.0.0.1.
-You can also log your own messages directly into the log file from your code
-using the Ruby logger class from inside your controllers. Example:
-  class WeblogController < ActionController::Base
-    def destroy
-      @weblog = Weblog.find(params[:id])
-      @weblog.destroy
-      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
-    end
-  end
-The result will be a message in your log file along the lines of:
-  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
-More information on how to use the logger is at http://www.ruby-doc.org/core/
-Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
-several books available online as well:
-* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
-* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
-These two books will bring you up to speed on the Ruby language and also on
-programming in general.
-== Debugger
-Debugger support is available through the debugger command when you start your
-Mongrel or WEBrick server with --debugger. This means that you can break out of
-execution at any point in the code, investigate and change the model, and then,
-resume execution! You need to install ruby-debug to run the server in debugging
-mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
-  class WeblogController < ActionController::Base
-    def index
-      @posts = Post.all
-      debugger
-    end
-  end
-So the controller will accept the action, run the first line, then present you
-with a IRB prompt in the server window. Here you can do things like:
-  >> @posts.inspect
-  => "[#<Post:0x14a6be8
-          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
-       #<Post:0x14a6620
-          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
-  >> @posts.first.title = "hello from a debugger"
-  => "hello from a debugger"
-...and even better, you can examine how your runtime objects actually work:
-  >> f = @posts.first
-  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
-  >> f.
-  Display all 152 possibilities? (y or n)
-Finally, when you're ready to resume execution, you can enter "cont".
-== Console
-The console is a Ruby shell, which allows you to interact with your
-application's domain model. Here you'll have all parts of the application
-configured, just like it is when the application is running. You can inspect
-domain models, change values, and save to the database. Starting the script
-without arguments will launch it in the development environment.
-To start the console, run <tt>rails console</tt> from the application
-directory.
-Options:
-* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
-  made to the database.
-* Passing an environment name as an argument will load the corresponding
-  environment. Example: <tt>rails console production</tt>.
-To reload your controllers and models after launching the console run
-<tt>reload!</tt>
-More information about irb can be found at:
-link:http://www.rubycentral.org/pickaxe/irb.html
-== dbconsole
-You can go to the command line of your database directly through <tt>rails
-dbconsole</tt>. You would be connected to the database with the credentials
-defined in database.yml. Starting the script without arguments will connect you
-to the development database. Passing an argument will connect you to a different
-database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
-PostgreSQL and SQLite 3.
-== Description of Contents
-The default directory structure of a generated Ruby on Rails application:
-  |-- app
-  |   |-- assets
-  |       |-- images
-  |       |-- javascripts
-  |       `-- stylesheets
-  |   |-- controllers
-  |   |-- helpers
-  |   |-- mailers
-  |   |-- models
-  |   `-- views
-  |       `-- layouts
-  |-- config
-  |   |-- environments
-  |   |-- initializers
-  |   `-- locales
-  |-- db
-  |-- doc
-  |-- lib
-  |   `-- tasks
-  |-- log
-  |-- public
-  |-- script
-  |-- test
-  |   |-- fixtures
-  |   |-- functional
-  |   |-- integration
-  |   |-- performance
-  |   `-- unit
-  |-- tmp
-  |   |-- cache
-  |   |-- pids
-  |   |-- sessions
-  |   `-- sockets
-  `-- vendor
-      |-- assets
-          `-- stylesheets
-      `-- plugins
-app
-  Holds all the code that's specific to this particular application.
-app/assets
-  Contains subdirectories for images, stylesheets, and JavaScript files.
-app/controllers
-  Holds controllers that should be named like weblogs_controller.rb for
-  automated URL mapping. All controllers should descend from
-  ApplicationController which itself descends from ActionController::Base.
-app/models
-  Holds models that should be named like post.rb. Models descend from
-  ActiveRecord::Base by default.
-app/views
-  Holds the template files for the view that should be named like
-  weblogs/index.html.erb for the WeblogsController#index action. All views use
-  eRuby syntax by default.
-app/views/layouts
-  Holds the template files for layouts to be used with views. This models the
-  common header/footer method of wrapping views. In your views, define a layout
-  using the <tt>layout :default</tt> and create a file named default.html.erb.
-  Inside default.html.erb, call <% yield %> to render the view using this
-  layout.
-app/helpers
-  Holds view helpers that should be named like weblogs_helper.rb. These are
-  generated for you automatically when using generators for controllers.
-  Helpers can be used to wrap functionality for your views into methods.
-config
-  Configuration files for the Rails environment, the routing map, the database,
-  and other dependencies.
-db
-  Contains the database schema in schema.rb. db/migrate contains all the
-  sequence of Migrations for your schema.
-doc
-  This directory is where your application documentation will be stored when
-  generated using <tt>rake doc:app</tt>
-lib
-  Application specific libraries. Basically, any kind of custom code that
-  doesn't belong under controllers, models, or helpers. This directory is in
-  the load path.
-public
-  The directory available for the web server. Also contains the dispatchers and the
-  default HTML files. This should be set as the DOCUMENT_ROOT of your web
-  server.
-script
-  Helper scripts for automation and generation.
-test
-  Unit and functional tests along with fixtures. When using the rails generate
-  command, template test files will be generated for you and placed in this
-  directory.
-vendor
-  External libraries that the application depends on. Also includes the plugins
-  subdirectory. If the app has frozen rails, those gems also go here, under
-  vendor/rails/. This directory is in the load path.

data/spec/shared_engine/MIT-LICENSE DELETED

@@ -1,20 +0,0 @@
-Copyright 2012 YOURNAME
-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.

data/spec/shared_engine/README.rdoc DELETED

@@ -1,3 +0,0 @@
-= SharedEngine
-This project rocks and uses MIT-LICENSE.