Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 605535
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T17:09:23+00:00 2026-05-13T17:09:23+00:00

At the moment I store each option in its own class attribute but this

  • 0

At the moment I store each option in its own class attribute but this leads to hard to read code when I need to access the passed options from instance methods.

For example if I pass a column name as an option I have to use self.send(self.class.path_finder_column) to get the column value from an instance method.

Notice I have prefixed the class attribute with the name of my plugin to prevent name clashes.

Here is a simple code example of a plugin which is passed an option, column, which is then accessed from the instance method set_path. Can the getters/setters be simplified to be more readable?

# usage: path_find :column => 'path'

module PathFinder    
  def path_finder(options = {})
    send :include, InstanceMethods

    # Create class attributes for options 
    self.cattr_accessor :path_finder_column
    self.path_finder_column = options[:column]

    module InstanceMethods
      def set_path        
        # setter
        self.send(self.class.path_finder_column + '=', 'some value')
        # getter
        self.send(self.class.path_finder_column)
      end
    end
  end 
end

ActiveRecord::Base.send :extend, PathFinder
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-13T17:09:24+00:00Added an answer on May 13, 2026 at 5:09 pm

    You can generate all those methods at runtime.

    module PathFinder
      def path_finder(options = {})
    
        # Create class attributes for options 
        self.cattr_accessor :path_finder_options
        self.path_finder_options = options
    
        class_eval <<-RUBY
          def path_finder(value)
            self.#{options[:column]} = value
          end
    
          def path_finder
            self.#{options[:column]}
          end
        RUBY
      end
    end
    
    ActiveRecord::Base.send :extend, PathFinder
    

    Unless you need to store the options, you can also delete the lines

    self.cattr_accessor :path_finder_options
    self.path_finder_options = options
    

    Note that my solution doesn’t need a setter and a getter as long as you always use path_finder and path_finder=.
    So, the shortest solution is (assuming only the :column option and no other requirements)

    module PathFinder
      def path_finder(options = {})
    
        # here more logic
        # ...
    
        class_eval <<-RUBY
          def path_finder(value)
            self.#{options[:column]} = value
          end
    
          def path_finder
            self.#{options[:column]}
          end
        RUBY
      end
    end
    
    ActiveRecord::Base.send :extend, PathFinder
    

    This approach is similar to the one adopted by acts_as_list and acts_as_tree.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I need to store some data in a file. FOR THE MOMENT each record
I am trying to write some code that will open a file, read its
At the moment I write stored procedures this way: create proc doStuff @amount int
At the moment inside the class I have ArrayList which the objects are stored
At the moment I am only able to output this to a string, although
At this moment I use this scenario to load OpenGL texture from PNG: load
At the moment my code (PHP) has too many SQL queries in it. eg...
I'm having hard time with this project, I'm building a boat configurator which is
I need to store hashes of passwords on disk. I am not entirely sure
I need to play sounds (~5 seconds each) throughout my iphone application. When they're

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.