BETAmodules.com is in beta — open to partnerships & joint ventures.Build with us
modules.com
⌘K

record-collection

v0.1.1424652988RubyGems· Ruby

Exposing ActiveRecord::Relations from your controllers to views is bad for business. As much as it is convenient to do so, does it really make sense that your view can use an `unscoped` version of it? More importantly, testing what is and isn't in scope of a `ActiveRecord::Relation` is REALLY hard.

The verdict
Abandoned. Last published 11 years ago. No recent activity — look for a maintained alternative.
No recent activity — look for a maintained alternative.
Live from the RubyGems registry · derived rules, not AI
How it scores
MaintenanceAbandoned
PopularityNiche
SecurityClean
LicensePermissive
DepsZero deps
Maintenance
Last published 11 years ago.
Popularity
6 downloads / week
Security
No known advisories for this version (OSV).
License
MIT
Dependencies
No runtime dependencies
Recent releases
  • 0.1.142465298811 years ago
  • 0.1.142458085311 years ago
  • 0.1.142458054511 years ago
  • 0.1.142457996311 years ago
  • 0.1.142457915111 years ago
  • 0.1.142457811811 years ago
  • 0.1.142457753111 years ago
  • 0.1.142454220411 years ago
record-collection — Exposing ActiveRecord::Relations from your controllers to views is bad for business. As much as it is convenient to do so, does it really make sense that your view can use an `unscoped` version of it? More importantly, testing what is and isn't in scope of a `ActiveRecord::Relation` is REALLY hard. (Ruby / RubyGems) · Modules