record-collection 0.0.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (3) hide show
  1. checksums.yaml +7 -0
  2. data/lib/record_collection.rb +0 -0
  3. metadata +75 -0
checksums.yaml ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA1:
3
+ metadata.gz: 7c14c60b1f94db3921dfc319bfcf41b930388bff
4
+ data.tar.gz: 9a0c7349b12faf876bdfa243dc82ef98eb518b97
5
+ SHA512:
6
+ metadata.gz: 3ece2f4749748d4369ff70171b69d0bceded21924611c3f758b492f53c9f414696f7d75ca258c9c020ee7454f560f46a3e8775ce3b3d2ef65b7caffa87bd058c
7
+ data.tar.gz: 4548b0c96558df2fa304e0530b35ec2d0ffe3f78fce040a526afb65c2f211eab6f55a206b09494b3558b6e998e116ba5bfe838130b09c7eb4ed66522e67a2496
File without changes
metadata ADDED
@@ -0,0 +1,75 @@
1
+ --- !ruby/object:Gem::Specification
2
+ name: record-collection
3
+ version: !ruby/object:Gem::Version
4
+ version: 0.0.0
5
+ platform: ruby
6
+ authors:
7
+ - Courtney de Lautour
8
+ autorequire:
9
+ bindir: bin
10
+ cert_chain: []
11
+ date: 2015-02-20 00:00:00.000000000 Z
12
+ dependencies:
13
+ - !ruby/object:Gem::Dependency
14
+ name: rspec
15
+ requirement: !ruby/object:Gem::Requirement
16
+ requirements:
17
+ - - "~>"
18
+ - !ruby/object:Gem::Version
19
+ version: '3'
20
+ type: :development
21
+ prerelease: false
22
+ version_requirements: !ruby/object:Gem::Requirement
23
+ requirements:
24
+ - - "~>"
25
+ - !ruby/object:Gem::Version
26
+ version: '3'
27
+ - !ruby/object:Gem::Dependency
28
+ name: activerecord
29
+ requirement: !ruby/object:Gem::Requirement
30
+ requirements:
31
+ - - "~>"
32
+ - !ruby/object:Gem::Version
33
+ version: '4'
34
+ type: :development
35
+ prerelease: false
36
+ version_requirements: !ruby/object:Gem::Requirement
37
+ requirements:
38
+ - - "~>"
39
+ - !ruby/object:Gem::Version
40
+ version: '4'
41
+ description: |2
42
+ Exposing ActiveRecord::Relations from your controllers to views is bad for business. As much as it is convenient to
43
+ do so, does it really make sense that your view can use an `unscoped` version of it? More importantly, testing what is
44
+ and isn't in scope of a `ActiveRecord::Relation` is REALLY hard.
45
+ email: courtney.de.lautour@gmail.com
46
+ executables: []
47
+ extensions: []
48
+ extra_rdoc_files: []
49
+ files:
50
+ - lib/record_collection.rb
51
+ homepage: https://github.com/Amerdrix/RecordCollection
52
+ licenses:
53
+ - MIT
54
+ metadata: {}
55
+ post_install_message:
56
+ rdoc_options: []
57
+ require_paths:
58
+ - lib
59
+ required_ruby_version: !ruby/object:Gem::Requirement
60
+ requirements:
61
+ - - ">="
62
+ - !ruby/object:Gem::Version
63
+ version: '0'
64
+ required_rubygems_version: !ruby/object:Gem::Requirement
65
+ requirements:
66
+ - - ">="
67
+ - !ruby/object:Gem::Version
68
+ version: '0'
69
+ requirements: []
70
+ rubyforge_project:
71
+ rubygems_version: 2.4.3
72
+ signing_key:
73
+ specification_version: 4
74
+ summary: Don't expose `ActiveRecord::Relation`s from controllers, expose `RecordCollections`!
75
+ test_files: []