Skip to main content

How to implement dependent dropdowns in Rails 4 with an unobtrusive jQuery script ?

How to implement dependent dropdowns in Rails 4 with an unobtrusive jQuery script?

class SpecializationType < ActiveRecord::Base
  # FIELDS
  # RELATIONS
  has_many :specializations
  # TRIGGERS
  # VALIDATIONS
  validates :name, :presence => true
  validates :description, :presence => true
  # SCOPES
  # OTHER
  def to_s
    name
  end
end


class Specialization < ActiveRecord::Base
  # FIELDS
  # RELATIONS
  belongs_to :specialization_type
  has_and_belongs_to_many :users
  # TRIGGERS
  # VALIDATIONS
  validates :name, :presence => true
  validates :description, :presence => true
  validates :specialization_type, :presence => true
  # SCOPES
  # OTHER
  def to_s
    name
  end
end

in views
<%= form_tag users_path, {:method => :get, :class => "users_search_form"} do %>
      <%= select_tag :specialization_type_id, options_from_collection_for_select(SpecializationType.all, "id", "name"), :prompt => "Select a specialization type" %>
      <%= select_tag :specialization_id, options_from_collection_for_select([], "id", "name"),
                     "data-option-dependent" => true,
                     "data-option-observed" => "specialization_type_id",
                     "data-option-url" => "/specialization_types/:specialization_type_id:/specializations.json",
                     "data-option-key-method" => :id,
                     "data-option-value-method" => :name %>
      <br/>
      <%= submit_tag "Cerca" %>
  <% end %>

  In particular:

“data-option-dependent” => true, indicates that this depends on a dropdown dropdown father
“data-option-observed” => “specialization_type_id”, specifies the id of the dropdown to be monitored. If its value changes, we’ll trigger the request to the server
“data-option-url” => “/specialization_type/:specialization_type_id:/specializations.json” is the url that we are going to call on the server. The script will replace :specialization_type_id: the id of the selected item in the dropdown father.
“data-option-key-method” => :id, indicates that we’ll use the ID field of the json returned by the server as attribute “key” for < option >
“data-option-value-method” => :name, indicates that we’ll use the NAME field in the json returned by the server as attribute “value” of < option >

Let’s add this jQuery script in the application.js file, in order to handle all dependent dropdown of our code

jQuery(document).ready(function () {
        $('select[data-option-dependent=true]').each(function (i) {
            var observer_dom_id = $(this).attr('id');
            var observed_dom_id = $(this).data('option-observed');
            var url_mask = $(this).data('option-url');
            var key_method = $(this).data('option-key-method');
            var value_method = $(this).data('option-value-method');
            var prompt = $(this).has('option[value=]').size() ? $(this).find('option[value=]') : $('<option value=\"\">').text('Select a specialization');
            var regexp = /:[0-9a-zA-Z_]+:/g;
            var observer = $('select#' + observer_dom_id);
            var observed = $('#' + observed_dom_id);

            if (!observer.val() && observed.size() > 1) {
                observer.attr('disabled', true);
            }
            observed.on('change', function () {
                observer.empty().append(prompt);
                if (observed.val()) {
                    url = url_mask.replace(regexp, observed.val());
                    $.getJSON(url, function (data) {
                        $.each(data, function (i, object) {
                            observer.append($('<option>').attr('value', object[key_method]).text(object[value_method]));
                            observer.attr('disabled', false);
                        });
                    });
                }
            });
        });
    });

    routes ---> 1
   
get "specialization_types/:specialization_type_id/specializations" => "application#specializations", :as => "specializations", :format => :json

def specializations
  specialization_type = SpecializationType.find(params[:specialization_type_id])
  respond_to do |format|
    format.json { render :json => specialization_type.specializations }
  end
end

Comments

Popular posts from this blog

Error malloc(): memory corruption nginx with passenger?

Error malloc(): memory corruption nginx with passenger Passenger issue resolving steps :  sudo gem uninstall passenger(uninstall all passenger) sudo gem install passenger sudo passenger-install-nginx-module --auto --auto-download --prefix=/opt/nginx --extra-configure-flags=none Update nginx config file with new passenger version and restart the nginx

PayUMoney Integration in Ruby on Rails

PayUMoney Integration in Ruby on Rails Generating Cheksum in Payu    Hash or Checksum = sha512(key|txnid|amount|productinfo|firstname|email|u df1|udf2|udf3|udf4|udf5||||||salt) Controller Code Will be def payumoney   @key = "gtKFFx"   @salt =  "eCwWELxi"   val = "#{key|txnid|amount|productinfo|firstname|email|u df1|udf2|udf3|udf4|udf5||||||#{@salt}"  @checksum = Digest::SHA512.hexdigest("#{val}") end <form action="https://test.payu.in/_payment" method='post' id='sub'  >     <input type="hidden" name="key" value="<%=@key%>">     <input type="hidden" name="hash" value="<%=@checksum%>">     <input type="hidden" name="txnid" value="TXN1234">     <input type="hidden" name="amount" value="200">     <input type="hidden" name=...

RSPEC TESTCASES FOR MODEL VALIDATIONS IN RAILS

describe User do    before(:each) do     @user_new = { :name => "chinna",:email => "chinna@yopmail.com",:password => "chinnaram",:password_confirmation => "chinnaram"}    end it "should create a new user details" do      @user_attr = User.create!(@user_new) end ##validations in your model ########### User.rb(your model your mention like that....) validates :name,:email,:presence => true validates :name,:uniqueness => true validates_attachment_content_type :image, :content_type => ['image/jpeg', 'image/png','image/pjpeg','image/x-png','image/gif'] ###validation for name presence it "should require a name" do      user = User.new(@user_attr.merge(:name => ""))      user.should_not be_valid   end #validation for email presence  it "should require a email" do      user = User.new(@user_attr.merge(:email => ""))      user...