Daniel-Hug

// get nearest parent element matching selector
var closest = (function() {
	var el = HTMLElement.prototype;
	var matches = el.matches || el.webkitMatchesSelector || el.mozMatchesSelector || el.msMatchesSelector;

	return function closest(el, selector) {
		return matches.call(el, selector) ? el : closest(el.parentElement, selector);
	};
})();

rmurphey

// 1: how could you rewrite the following to make it shorter?
if (foo) {
  bar.doSomething(el);
} else {
  bar.doSomethingElse(el);
}

Couto

var webpack = require('webpack');
var HtmlWebpackPlugin = require('html-webpack-plugin');
var path = require('path');
var folders = {
    APP: path.resolve(__dirname, '../app'),
    BUILD: path.resolve(__dirname, '../build'),
    BOWER: path.resolve(__dirname, '../bower_components'),
    NPM: path.resolve(__dirname, '../node_modules')
};

datchley

let isFunction = function(obj) {
    return typeof obj == 'function' || false;
};

class EventEmitter {
  constructor() {
    this.listeners = new Map();
  }
  addListener(label, callback) {
    this.listeners.has(label) || this.listeners.set(label, []);

mcevskb

// Run in console on the history page (http://trakt.tv/users/<username>/history)
// Will remove all the duplicate episodes, on that page, from the watched history.

var episodesRemoved = []
// episodeItems = $("[data-type=episode]")
episodeItems.each(function(){
  var $this = $(this);
  var episodeId = $this.data('episode-id')
  var showId = $this.data('show-id')

codingwithchris

Access Control (Creating a Secure and Trusted Application)

Access control is critical to the security of our application. Beyond proper credential encryption, hashing, SALTing etc, access control is the next line of defense in protecting our users data.

Role Based Access Control Methodology (RBAC)

When giving elevated access to a User for a particular part of the system, we use a methodology called RBAC. This means that we create Roles where we assign permissions and apply filter policies. These Roles then get assigned to Users who have their CRUD access to Lists, Records, and Fields determined accordingly.

Our Access Control Philosophy

Gonzillaaa

page.includeJs("http://www.google.com/jsapi?key=AIzaSyA5m1Nc8ws2BbmPRwKu5gFradvD_hgq6G0", function() {
  page.evaluate(function() {
        
        google.load("feeds", "1");
        var feed = new google.feeds.Feed("http://www.digg.com/rss/index.xml");
        
        feed.includeHistoricalEntries(); // tell the API we want to have old entries too
        feed.setNumEntries(250); // we want a maximum of 250 entries, if they exist
        feed.load();
        

TheRealFlyingCoder

So once you figure out all the caveats, running Keystone on Docker and in Fly.io is relatively simple.

package.json:

You need --fix on your setup script for Docker to auto update the schemas

"setup": "keystone postinstall --fix"

NOTES FOR DOCKER:
1. I use Yarn V3 in a monorepo hence the corepack lines and project structure

fwielstra

/* The API controller
   Exports 3 methods:
   * post - Creates a new thread
   * list - Returns a list of threads
   * show - Displays a thread and its posts
*/


var Thread = require('../models/thread.js');
var Post = require('../models/post.js');

PatrickJS

var EventEmitter = require('events').EventEmitter;
var _ = require('lodash');

// Factory shared
var makePerson = function() {
  var person = {};
  EventEmitter.call(person);
  person.wallet = 0;
  _.extend(person, personMethods)
  return person;