oconn

call() and apply()

The apply() method calls a function with a given this value and arguments provided as an array (or an array-like object).

The call() method calls a function with a given this value and arguments provided individually.

var tickerOne = {
  count : 1,
  getCount : function(){

oconn

Functions

Defining functions

var functionOne = function(){};

vs

oconn

Javascript Arguments

Javascript arguments are stored in an array like structure where indicies can be accesses using bracket notation, however none of the objects properties are available except length.

function args(){
  return arguments;
}

oconn

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

oconn

(ns battlebots.constants.arena)

(def arena-key {:open   {:type "open"
                         :display " "
                         :transparent true}
                :ai     {:type "ai"
                         :display "@"
                         :transparent true
                         :energy 20}
                :block  {:type "block"

oconn

import { append, equals, map, merge, omit, pluck, prepend, reject, zipObj } from 'ramda';

/**
 * @method itemByKey
 *
 * pulls an items key and asigns itself to its key
 */
export const itemByKey = (item, key = '_id') => {
    return { [item[key]]: item };
};

oconn

export const REQUEST_DELETE_USER = 'REQUEST_DELETE_USER';
export const USER_REMOVE_USER = 'USER_REMOVE_USER';

export const removeUser = (userId) => {
    return (dispatch, getState) => {
        // The middleware picks up on the following signature
        // 
        // 1. request prop
        // 2. request prop is thenable
        // 

oconn

;; Goal 
;; In this example, I want to be able to say that parent route "/users" requires the admin role. I then specify 
;; on a case by case basis that a specific child route also allows additional permissions. ex: "users/:user-id" also 
;; allows the user role. 
;;
;; Problem
;; A user that only contains the "user" role will not be allowed to access the "user/get-user-by-id" handler because 
;; the authorize interceptor at "/users" will run first. 
;;
;; Proposed Solution 

oconn

{
  "global-coords": [
    6,
    6
  ],
  "arena": [
    [
      {
        "contents": {
          "type": "open",

oconn

{:deps {org.clojure/clojurescript {:mvn/version "1.10.520"}
        lilactown/hx {:local/root "../../opensource/hx"}
        
        com.bhauman/figwheel-main {:mvn/version "0.2.0"}
        com.bhauman/rebel-readline-cljs {:mvn/version "0.1.4"}}
 :paths ["src" "resources" "target"]
 :aliases {:build {:main-opts ["--main" "cljs.main"
                               "--compile-opts" "prod.cljs.edn"
                               "--compile"]}
           :dev {:main-opts ["--main" "figwheel.main"