Project

rails-js

0.0
No commit activity in last 3 years
No release in over 3 years
There's a lot of open issues
Divide your javascript like you divide your ruby code. Put it in controllers and actions and write clean, scalable code. DEPRECATION WARNING: Gem has been renamed to 'rails-js-routes' for better findability.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 0.7
~> 1.3
~> 0.8

Runtime

~> 4
 Project Readme

rails-js-routes

Build Status Dependency Status Gem Version License

NOTICE: We decided to rename this gem from rails-js to rails-js-routes as it was nearly impossible to find.

I worked on several Rails projects and there were many cases when it felt overkill to use a framework like Angular or Ember, because javascript was only needed in some parts of the application. But by not using these frameworks I had to think of a way to structure the code by myself. I came up with the conclusion to organize the javascript code like the ruby code is organized, that means: Split up in controllers, which are split up in actions.

How it works

  • In rails-js-routes we are able to define controllers, as well as helpers.
  • Controllers have actions which are executed when the matching rails action is executed.
  • Helpers should be clear. Pretty much like the rails helpers. There are helper per controller and global helpers.
  • The gem also provides a view helper to use in your layouts, which passes the routing information to rails-js-routes.

You start by creating an app.

//= require routes

/*
 * app/assets/javascripts/application.js
 */

Rails.app({
  // Define global helpers here
  helper: function() {
  }
},
// Put in initial data
{
  foo: 'bar'
},
// A function that is executed before every action
function() {
  console.log('beforeAll() executed');
});

Create controllers accordingly.

/*
 * app/assets/javascripts/controllers/users.js
 */

Rails.controller('users', {
  // actions here
  new: function(h) {
    // execute helper
    h.awesomeHelper();
  },

  index: function(h) {
    // Do the same as in new()
    this.index(h);
  }
},
{
  // helpers here
  awesomeHelper: function() {
  }
});

Use code from other controllers.

/*
 * app/assets/javascripts/controllers/admin/users.js
 */

Rails.controller('admin/users', {
  new: function(h) {
    // Execute action of foreign controller
    R.action('users#new');
  },

  index: function(h) {
    // Execute foreign helper with arguments
    R.helper('users', 'awesomeHelper', 1, 2, 3);

    // Execute global helper with arguments
    R.global('helper', 1, 2, 3);
  }
},{});

Global variables without the mess.

/*
 * Use R singleton everywhere
 */

// Setting
R('answer', 42);
// Multiple levels
R('a.global.variable', 'foo');

// Getting
console.log(R('a.global.variable'));

Define hooks for namespaces.

/*
 * app/assets/javascripts/namespaces/admin.js
 */

Rails.namespace('admin', function() {
  // Will be executed on all admin routes (e.g. admin/users#new)
  console.log('Hello Mr. Admin');
});

For more info...

...just read in app/assets/javascripts/routes.js. I tried my best and documented nearly every line of code :)

Installing

Install it as any other gem by putting this to your Gemfile:

gem 'rails-js-routes'

In your layouts, put this line into the head:

<%= js_routes %>

Also make sure to include routes in your application.js. If you are using Turbolinks, make sure to include routes after turbolinks.

Testing

Javascript tests are in test/dummy/spec/javascripts/rails-js-routes_spec.js. They are executed using rake teaspoon (by using the teaspoon runner). I'm still trying to get travis to execute the teaspoon tests properly...

Contributing

Fork -> Commit -> Pull Request

This project uses the Airbnb Styleguide as our coding guideline. We think this is a good piece of work and worth spreading. In case of any doubts refer to the style used around.