active-hash / active-hash/active_hash

Support associations

Open
#118 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

v2.0.0
Dominant language
Ruby
Stars
1.4k
Forks
186
PR merge metrics
No merged PRs in 30d

Description

@flavorjones @zilkey

It would be nice to move on to newer standards:

Add:

  • where(:name => ["super", "secret"]).order(:name)
  • where(:other => {:name => "user"}).order(:id).first

Deprecate:

  • find_by_name_and_country
  • find(:all, :conditions => {:name => "super"})
  • drop rails 2.x
  • drop ruby 1.8.7 (and 1.9.3)?

What do you think about deprecating these older standards?
I'm up for the work.
Just want your take on whether this is a good direction.

--Keenan

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the repository's existing association and query APIs, then compare them with the proposed where/order examples and the Rails 2.x and Ruby compatibility items. Done would require an agreed scope, implemented support, and a documented deprecation plan.

Written by the indexing model from the issue text.

Assessment

Tech stack
rails, ruby
Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.