dao 5.5.0 → 8.0.0

data/wrap-1.5.2/wrap.gemspec

@@ -0,0 +1,38 @@
+## wrap.gemspec
+#
+
+Gem::Specification::new do |spec|
+  spec.name = "wrap"
+  spec.version = "1.5.2"
+  spec.platform = Gem::Platform::RUBY
+  spec.summary = "wrap"
+  spec.description = "non-sucking :before and :after filters for any ruby class"
+  spec.license = "same as ruby's"
+
+  spec.files =
+["README",
+ "Rakefile",
+ "lib",
+ "lib/wrap.rb",
+ "test",
+ "test/testing.rb",
+ "test/wrap_test.rb",
+ "wrap.gemspec"]
+
+  spec.executables = []
+  
+  spec.require_path = "lib"
+
+  spec.test_files = nil
+
+  
+    spec.add_dependency(*["map", " >= 4.7.1"])
+  
+
+  spec.extensions.push(*[])
+
+  spec.rubyforge_project = "codeforpeople"
+  spec.author = "Ara T. Howard"
+  spec.email = "ara.t.howard@gmail.com"
+  spec.homepage = "https://github.com/ahoward/wrap"
+end

metadata

@@ -1,167 +1,100 @@
 --- !ruby/object:Gem::Specification
 name: dao
 version: !ruby/object:Gem::Version
-  version: 5.5.0
+  version: 8.0.0
 platform: ruby
 authors:
 - Ara T. Howard
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-04-24 00:00:00.000000000 Z
+date: 2020-10-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.1'
+        version: '6.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.1'
+        version: '6.0'
 - !ruby/object:Gem::Dependency
   name: map
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 6.0.0
+        version: '6.6'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 6.0.0
+        version: '6.6'
 - !ruby/object:Gem::Dependency
   name: fattr
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '2.2'
+        version: '2.4'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '2.2'
-- !ruby/object:Gem::Dependency
-  name: coerce
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: 0.0.3
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: 0.0.3
+        version: '2.4'
 - !ruby/object:Gem::Dependency
   name: tagz
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 9.9.2
+        version: '9.10'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 9.9.2
-- !ruby/object:Gem::Dependency
-  name: multi_json
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: 1.0.3
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: 1.0.3
-- !ruby/object:Gem::Dependency
-  name: uuidtools
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: 2.1.2
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: 2.1.2
-- !ruby/object:Gem::Dependency
-  name: wrap
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: 1.5.0
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: 1.5.0
+        version: '9.10'
 - !ruby/object:Gem::Dependency
   name: rails_current
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: 1.8.0
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: 1.8.0
-- !ruby/object:Gem::Dependency
-  name: rails_errors2html
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ! '>='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.3.0
+        version: '2.2'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.3.0
-description: presenter, conducer, api, and better form objects for you rails' pleasure
+        version: '2.2'
+description: presenter, conductor, api, and better form objects for you rails' pleasure
 email: ara.t.howard@gmail.com
 executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- Gemfile
-- Gemfile.lock
-- README
+- README.md
 - Rakefile
+- coerce-0.0.8/README
+- coerce-0.0.8/Rakefile
+- coerce-0.0.8/coerce.gemspec
+- coerce-0.0.8/lib/coerce.rb
 - dao.gemspec
 - lib/dao.rb
+- lib/dao/_lib.rb
 - lib/dao/active_record.rb
 - lib/dao/api.rb
 - lib/dao/api/call.rb
@@ -171,6 +104,7 @@ files:
 - lib/dao/api/modes.rb
 - lib/dao/api/routes.rb
 - lib/dao/blankslate.rb
+- lib/dao/coerce.rb
 - lib/dao/conducer.rb
 - lib/dao/conducer/active_model.rb
 - lib/dao/conducer/attributes.rb
@@ -184,6 +118,7 @@ files:
 - lib/dao/endpoint.rb
 - lib/dao/engine.rb
 - lib/dao/errors.rb
+- lib/dao/errors2html.rb
 - lib/dao/exceptions.rb
 - lib/dao/extractor.rb
 - lib/dao/form.rb
@@ -219,20 +154,30 @@ files:
 - lib/dao/validations/common.rb
 - lib/dao/validations/instance.rb
 - lib/dao/validations/validator.rb
+- lib/dao/wrap.rb
+- tasks/default.rake
+- tasks/this.rb
 - test/active_model_conducer_lint_test.rb
 - test/api_test.rb
 - test/conducer_test.rb
 - test/data/han-solo.jpg
 - test/errors_test.rb
 - test/form_test.rb
-- test/helper.rb
 - test/leak.rb
+- test/rake_rerun_reporter.rb
 - test/support_test.rb
-- test/testing.rb
+- test/test_helper.rb
+- test/util.rb
 - test/validations_test.rb
+- wrap-1.5.2/README
+- wrap-1.5.2/Rakefile
+- wrap-1.5.2/lib/wrap.rb
+- wrap-1.5.2/test/testing.rb
+- wrap-1.5.2/test/wrap_test.rb
+- wrap-1.5.2/wrap.gemspec
 homepage: https://github.com/ahoward/dao
 licenses:
-- same as ruby's
+- Ruby
 metadata: {}
 post_install_message: 
 rdoc_options: []
@@ -240,17 +185,16 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ! '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ! '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: codeforpeople
-rubygems_version: 2.0.3
+rubygems_version: 3.1.2
 signing_key: 
 specification_version: 4
 summary: dao

data/Gemfile

@@ -1,16 +0,0 @@
-source 'https://rubygems.org'
-
-
-
-gem 'rails'             , ' >= 3.1'
-gem 'map'               , ' >= 6.0.0'
-gem 'fattr'             , ' >= 2.2'
-gem 'coerce'            , ' >= 0.0.3'
-gem 'tagz'              , ' >= 9.8'
-gem 'multi_json'        , ' >= 1.0.3'
-gem 'uuidtools'         , ' >= 2.1.2'
-gem 'wrap'              , ' >= 1.5.0'
-gem 'rails_current'     , ' >= 1.7.0'
-gem 'rails_errors2html' , ' >= 1.3.0'
-gem 'pry'
-

data/Gemfile.lock

@@ -1,118 +0,0 @@
-GEM
-  remote: https://rubygems.org/
-  specs:
-    actionmailer (3.2.13)
-      actionpack (= 3.2.13)
-      mail (~> 2.5.3)
-    actionpack (3.2.13)
-      activemodel (= 3.2.13)
-      activesupport (= 3.2.13)
-      builder (~> 3.0.0)
-      erubis (~> 2.7.0)
-      journey (~> 1.0.4)
-      rack (~> 1.4.5)
-      rack-cache (~> 1.2)
-      rack-test (~> 0.6.1)
-      sprockets (~> 2.2.1)
-    activemodel (3.2.13)
-      activesupport (= 3.2.13)
-      builder (~> 3.0.0)
-    activerecord (3.2.13)
-      activemodel (= 3.2.13)
-      activesupport (= 3.2.13)
-      arel (~> 3.0.2)
-      tzinfo (~> 0.3.29)
-    activeresource (3.2.13)
-      activemodel (= 3.2.13)
-      activesupport (= 3.2.13)
-    activesupport (3.2.13)
-      i18n (= 0.6.1)
-      multi_json (~> 1.0)
-    arel (3.0.2)
-    builder (3.0.4)
-    chronic (0.9.1)
-    coderay (1.0.9)
-    coerce (0.0.4)
-      chronic (>= 0.6.2)
-    erubis (2.7.0)
-    fattr (2.2.1)
-    hike (1.2.3)
-    i18n (0.6.1)
-    journey (1.0.4)
-    json (1.8.0)
-    mail (2.5.4)
-      mime-types (~> 1.16)
-      treetop (~> 1.4.8)
-    map (6.5.1)
-    method_source (0.8.1)
-    mime-types (1.23)
-    multi_json (1.7.6)
-    polyglot (0.3.3)
-    pry (0.9.12.2)
-      coderay (~> 1.0.5)
-      method_source (~> 0.8)
-      slop (~> 3.4)
-    rack (1.4.5)
-    rack-cache (1.2)
-      rack (>= 0.4)
-    rack-ssl (1.3.3)
-      rack
-    rack-test (0.6.2)
-      rack (>= 1.0)
-    rails (3.2.13)
-      actionmailer (= 3.2.13)
-      actionpack (= 3.2.13)
-      activerecord (= 3.2.13)
-      activeresource (= 3.2.13)
-      activesupport (= 3.2.13)
-      bundler (~> 1.0)
-      railties (= 3.2.13)
-    rails_current (1.7.0)
-      map (>= 6.0.1)
-    rails_errors2html (1.4.2)
-      fattr (>= 2.2.1)
-      map (>= 6.2.0)
-      rails_view (>= 1.0.1)
-    rails_view (1.0.1)
-    railties (3.2.13)
-      actionpack (= 3.2.13)
-      activesupport (= 3.2.13)
-      rack-ssl (~> 1.3.2)
-      rake (>= 0.8.7)
-      rdoc (~> 3.4)
-      thor (>= 0.14.6, < 2.0)
-    rake (10.0.4)
-    rdoc (3.12.2)
-      json (~> 1.4)
-    slop (3.4.5)
-    sprockets (2.2.2)
-      hike (~> 1.2)
-      multi_json (~> 1.0)
-      rack (~> 1.0)
-      tilt (~> 1.1, != 1.3.0)
-    tagz (9.9.1)
-    thor (0.18.1)
-    tilt (1.4.1)
-    treetop (1.4.14)
-      polyglot
-      polyglot (>= 0.3.1)
-    tzinfo (0.3.37)
-    uuidtools (2.1.4)
-    wrap (1.5.0)
-      map (>= 4.7.1)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  coerce (>= 0.0.3)
-  fattr (>= 2.2)
-  map (>= 6.0.0)
-  multi_json (>= 1.0.3)
-  pry
-  rails (>= 3.1)
-  rails_current (>= 1.7.0)
-  rails_errors2html (>= 1.3.0)
-  tagz (>= 9.8)
-  uuidtools (>= 2.1.2)
-  wrap (>= 1.5.0)

data/README

@@ -1,256 +0,0 @@
-NAME
-  dao
-
-SYNOPSIS
-  a sa-weet-ass library for structuring rails applications using the 'data
-  access object' design pattern.  dao consists of two main data access
-  objects, *api* objects and *conducer* objects.  conducers combine the
-  presenter pattern with the conductor pattern.
-
-
-  API
-
-    class Api < Dao::Api
-      call('/posts') do
-        get do
-          data[:posts] = Post.all.map{|post| post.attributes}
-        end
-
-        post do
-          post = Post.new(params[:post])
-
-          if post.save
-            data[:post] = post.attributes
-          else
-            status 420
-          end
-        end
-      end
-    end
-
-  CONDUCER
-
-    # TODO
-
-
-  wikipedia has this to say about dao in general
-
-    "
-      In computer software, a data access object (DAO) is an object that
-      provides an abstract interface to some type of database or other
-      persistence mechanism. By mapping application calls to the persistence
-      layer, DAOs provide some specific data operations without exposing
-      details of the database. This isolation supports the single
-      responsibility principle. It separates what data accesses the
-      application needs, in terms of domain-specific objects and data types
-      (the public interface of the DAO), from how these needs can be satisfied
-      with a specific DBMS, database schema, etc. (the implementation of the
-      DAO).
-    "
-      - http://en.wikipedia.org/wiki/Data_access_object
-
-  and this to say about the single responsibility principle
-
-    "
-      In object-oriented programming, the single responsibility principle
-      states that every class should have a single responsibility, and that
-      responsibility should be entirely encapsulated by the class. All its
-      services should be narrowly aligned with that responsibility.
-
-      Responsibility [is defined] as a reason to change, and [single
-      responsibility means] that a class or module should have one, and only
-      one, reason to change. As an example, consider a module that compiles and
-      prints a report. Such a module can be changed for two reasons. First,
-      the content of the report can change. Second, the format of the report
-      can change. These two things change for very different causes; one
-      substantive, and one cosmetic. The single responsibility principle says
-      that these two aspects of the problem are really two separate
-      responsibilities, and should therefore be in separate classes or
-      modules. It would be a bad design to couple two things that change for
-      different reasons at different times.
-    "
-      - http://en.wikipedia.org/wiki/Single_responsibility_principle
-
-  even though rails is the sweet, its ActiveRecord class violates (or, at
-  least, encourages a programmer to violate) the single responsibility
-  principle
-
-  this leads to obvious problems
-
-    "
-      Jim Weirich, at the end of his SOLID Ruby Talk at the 2009 Ruby
-      Conference, asks the audience: "ActiveRecord objects implement a domain
-      concept and a persistence concept. Does this violate the SRP (Single
-      Responsibility Principle)?" The audience agrees that it does violate the
-      SRP. Jim asks if this bothers them. Many members of the audience say
-      yes. Why? It makes testing harder. It makes the persistence object a lot
-      heavier.
-    "
-      - http://programmers.stackexchange.com/questions/119352/does-the-activerecord-pattern-follow-encourage-the-solid-design-principles#comment293734_119352
-
-  and subtle yet sweeping consequences (as described by uncle bob)
-
-    "
-      The problem I have with ActiveRecord is that it creates confusion about
-      ... two very different styles of programming. A database table is a
-      data structure. It has exposed data and no behavior. But an ActiveRecord
-      appears to be an object. It has “hidden” data, and exposed behavior. I
-      put the word “hidden” in quotes because the data is, in fact, not
-      hidden. Almost all ActiveRecord derivatives export the database columns
-      through accessors and mutators. Indeed, the Active Record is meant to be
-      used like a data structure.
-
-      On the other hand, many people put business rule methods in their
-      ActiveRecord classes; which makes them appear to be objects. This leads
-      to a dilemma. On which side of the line does the Active Record really
-      fall? Is it an object? Or is it a data structure?
-
-      This dilemma is the basis for the oft-cited impedance mismatch between
-      relational databases and object oriented languages. Tables are data
-      structures, not classes. Objects are encapsulated behavior, not database
-      rows.
-
-      ...
-
-      The problem is that Active Records are data structures. Putting business
-      rule methods in them doesn’t turn them into true objects. In the end,
-      the algorithms that employ ActiveRecords are vulnerable to changes in
-      schema, and changes in type. They are not immune to changes in type, the
-      way algorithms that use objects are.
-
-      ...
-
-      So applications built around ActiveRecord are applications built around
-      data structures. And applications that are built around data structures
-      are procedural—they are not object oriented. The opportunity we miss
-      when we structure our applications around ActiveRecord is the
-      opportunity to use object oriented design.
-    "
-      - https://sites.google.com/site/unclebobconsultingllc/active-record-vs-objects
-
-  and a clear solution (again, uncle bob)
-
-    "
-      I am not recommending against the use of ActiveRecord. I think the
-      pattern is very useful. What I am advocating is a separation between the
-      application and ActiveRecord.
-
-      ActiveRecord belongs in the layer that separates the database from the
-      application. It makes a very convenient halfway-house between the hard
-      data structures of database tables, and the behavior exposing objects in
-      the application.
-
-      Applications should be designed and structured around objects, not data
-      structures. Those objects should expose business behaviors, and hide any
-      vestige of the database.
-    "
-      - https://sites.google.com/site/unclebobconsultingllc/active-record-vs-objects
-
-  welcome to the dao
-
-
-DESCRIPTION
-
-  API
-    applications that are written on dao look like this in ruby
-
-      result = api.call('/posts/new', params)
-
-    and like this in javascript
-
-      result = api.call('/posts/new', params)
-
-    in command-line applications they look like this
-
-      result = api.call('/posts/new', params)
-
-    and in tests this syntax is used
-
-      result = api.call('/posts/new', params)
-
-    when a developer wants to understand the interface of a dao application
-    she does this
-
-      vi app/api.rb
-
-    when a developer of a dao application wants to play with a dao application
-    interactively she does
-
-      (rails console)
-
-      > api = Api.new result = api.call('/posts/new', params)
-
-    when a remote client wants to understand the api of a dao application she
-    does
-
-      curl --silent http://dao.app.com/api | less
-
-
-
-    this kind of brutally consistent interface is made possible by structuring
-    access to data around the finest data structure of all time - the hash.
-    in the case of dao the hash is a well structured and slightly clever hash,
-    but a simple hash interface is the basis of every bit of goodness dao has
-    to offer.
-
-    in dao, application developers do not bring models into controllers and,
-    especially not into views.  instead, a unified interface to application
-    logic and data is used everywhere: in tests, in controllers, from the
-    command-line, and also from javascript.
-
-    this seperation of concerns brings with it many, many desirable qualities:
-
-      - total seperation of concerns between the front and back end of a web
-        application.  when developers are using dao changes to the data model
-        have zero effect on controllers and views.
-
-      - issues related to having models in controllers and views such as
-        difficulty reasoning about caching and n+1 queries in views killing
-        the db simply disappear.
-
-      - bad programming practices like using quasi-global variables
-        (current_user) or decorating models with view specific attributes
-        (password_verification) are no longer needed.
-
-      - developers are able to reason over the abilities of an application by
-        reading only a few source files.
-
-      - databases can be swapped, mixed, or alternate storage/caching
-        mechanisms added at any time without affecting the application's
-        controllers or views.
-
-      - transition from form based views to semi-ajax ones to fully-ajax ones
-        is direct.
-
-      - forms and interfaces that involve dozens of models are as easy to deal
-        with as simple ones.
-
-      - code can be optimized at the interface.
-
-READING
-  http://blog.plataformatec.com.br/2012/03/barebone-models-to-use-with-actionpack-in-rails-4-0/
-  http://martinfowler.com/eaaCatalog/serviceLayer.html
-  http://blog.firsthand.ca/2011/10/rails-is-not-your-application.html
-  http://best-practice-software-engineering.ifs.tuwien.ac.at/patterns/dao.html
-  http://www.codefutures.com/data-access-object/
-  http://java.sun.com/blueprints/corej2eepatterns/Patterns/DataAccessObject.html
-  http://www.paperplanes.de/2010/5/7/activerecord_callbacks_ruined_my_life.html
-  http://google-styleguide.googlecode.com/svn/trunk/jsoncstyleguide.xml
-  http://pragdave.blogs.pragprog.com/pragdave/2007/03/the_radar_archi.html
-  http://borisstaal.com/post/22586260753/mvc-in-a-browser-vs-reality
-
-
-INSTALL
-  gem 'dao', :path => File.expand_path('..') ### Gemfile
-  rails generate dao api
-  vim -o app/api.rb app/controllers/api_controller.rb
-  curl --silent http://0.0.0.0:3000/api
-  curl --silent http://0.0.0.0:3000/api/ping
-
-HISTORY
-  4.0.0
-    - dao depends has tied itself to rails, for better or worse...
-    - drop custom form encoding.  just use a rack-like approach.
-    - dao form parameter encoding has changed slightly to 'dao[/api/path][x,y,z]=42'
-    - dao form paramters are now preparsed in a before filter
-