iheanyi

get 'users/confirm', :to => "api/v1/users/confirmations#show", as: 'confirm'

# <%= confirm_url(@resource) %> as localhost:3000/users/confirm.1 (or whatever the id is). Any idea why?

iheanyi

class ApplicationController < ActionController::Base
  #include Clearance::Controller
  # Prevent CSRF attacks by raising an exception.
  # For APIs, you may want to use :null_session instead.
  protect_from_forgery with: :null_session, if: Proc.new { |c| c.request.format == 'application/json' }
  before_filter :authenticate_user_from_token!

  private
    def authenticate_user_from_token!
      authenticate_with_http_token do |token, options|

iheanyi

First Letter

First Letter: Spacing Class (p or m)
Second Letter: Direction/Position (v/h, t/l/r/b)
Third Letter: Size (s (small), m (medium), l (large)

Example:
pbs = Padding Bottom Small,
mb = Margin Bottom

iheanyi

{
	"bold_folder_labels": true,
	"caret_extra_bottom": 2,
	"caret_extra_top": 2,
	"caret_extra_width": 2,
	"caret_style": "phase",
	"color_scheme": "Packages/User/SublimeLinter/base16-ocean.dark (SL).tmTheme",
	"draw_white_space": "all",
	"fade_fold_buttons": false,
	"file_exclude_patterns":

iheanyi

Main Question

When should I start using a JS MVC framework for my front-end applications over a server-rendered application?

Ideas

When the UI/UX is somewhat complex

This means that you have nested routes or various components on your website that depend on data retrieved from the back-end. I found it harder to build maintable, ambitious UIs using only JQuery without losing my sanity.

iheanyi

Think of Angular Modules as an Ember Application

This is what defines your application and which controllers are a part of it.

Think of Angular Controllers as Ember Controllers

You can see the similarities between Ember controllers and Angular controllers. Attributes and functions defined within the Angular controller are responsible for updating the view. Similar to how actions in the front-end and attributes in Ember controllers are responsible for updating Ember's views.

Think of Angular Directives as Ember Components

Directives in Angular can be seen as components in Ember.JS, isolated in scope, attributes, and their templates. <directive [args...]> = {{component [args...}}

iheanyi

class RecipeCreator
  attr_reader :recipe
  
  def initialize(params)
    @recipe = Recipe.new(params)
  end
  
  def save
    saved = recipes.save
    

iheanyi

App.AccountEditRoute = Ember.Route.extend({
  setupController: function(controller) {
    controller.set('content', this.get('currentUser'));
  }
});

iheanyi

require 'nokogiri'
require 'faraday'

@term = "201420"
@crn = "14433"
@crn = "21129"
@crn = "22091"

@conn = Faraday.new(:url => 'https://class-search.nd.edu/reg/srch/ClassSearchServlet') do |faraday|
  faraday.request :url_encoded

iheanyi

Building on this - experimenting with fake 3d svg arcs using two nested orthographic projections and cardinal line interpolation.