Simple Express Parameter Parsing Demo
git clone https://gist.github.com/a5656b01c35d6f25dda7.git demo
cd demo
npm install
npm start
Look at the purty code. See how the magic be done.
<!DOCTYPE html> | |
<!-- Written by William Hilton --> | |
<!-- Derived from the "Graceful Tree Conjecture" by NPashaP @ https://gist.github.com/NPashaP/7683252 --> | |
<head> | |
<meta charset="utf-8" /> | |
<!-- This is for the trash bin icon. --> | |
<link href="http://netdna.bootstrapcdn.com/font-awesome/4.1.0/css/font-awesome.min.css" rel="stylesheet" /> | |
<style> | |
.oval-box { | |
background: white; |
git clone https://gist.github.com/a5656b01c35d6f25dda7.git demo
cd demo
npm install
npm start
Look at the purty code. See how the magic be done.
/* Straight stolen from http://bl.ocks.org/dwtkns/4686432 */ | |
window.worlddata = {"type":"Topology","transform":{"scale":[0.03600360036003601,0.017366249624962495],"translate":[-180,-90]},"objects":{"land":{"type":"MultiPolygon","arcs":[[[0]],[[1]],[[2]],[[3]],[[4]],[[5]],[[6]],[[7,8]],[[9,10]],[[11]],[[12]],[[13]],[[14]],[[15]],[[16]],[[17]],[[18]],[[19]],[[20]],[[21]],[[22]],[[23]],[[24]],[[25]],[[26]],[[27]],[[28,29]],[[30]],[[31]],[[32]],[[33]],[[34]],[[35]],[[36]],[[37]],[[38]],[[39]],[[40]],[[41,42]],[[43]],[[44]],[[45]],[[46,47,48,49]],[[50]],[[51]],[[52]],[[53]],[[54]],[[55]],[[56]],[[57]],[[58]],[[59]],[[60]],[[61,62]],[[63]],[[64]],[[65]],[[66]],[[67]],[[68]],[[69]],[[70]],[[71]],[[72]],[[73]],[[74]],[[75,76]],[[77]],[[78]],[[79]],[[80]],[[81]],[[82]],[[83]],[[84]],[[85]],[[86]],[[87]],[[88]],[[89,90]],[[91]],[[92]],[[93]],[[94]],[[95]],[[96]],[[97]],[[98]],[[99]],[[100]],[[101]],[[102]],[[103]],[[104]],[[105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128, |
CREATE OR REPLACE FUNCTION upsert_user() | |
RETURNS trigger AS | |
$upsert_user$ | |
declare | |
existing record; | |
begin | |
if (select EXISTS(select 1 from users where user_id = NEW.user_id)) then | |
select user_name, user_class, user_age into strict existing from users where user_id = new.user_id; |
\documentclass{jhwhw} | |
\author{Christopher S. Corley} | |
\title{Class homework solutions} | |
\date{October 19, 2011} | |
\begin{document} | |
\problem{Some problem name} | |
blahblah | |
\solution |
/* | |
* Dict Object for JavaScript (https://gist.github.com/wmhilton/5859079) | |
* Author: William Hilton (wmhilton@gmail.com) | |
* License: http://opensource.org/licenses/MIT | |
* | |
* Say you want something like a Python "dictionary" or a Java "map" where you | |
* are storing (String key, Object value) pairs. It's tempting to do it using | |
* object properties in JavaScript, since | |
* obj['key'] = value | |
* works so conveniently. However, say you want to be able to have some properties |
// See comments below. | |
// This code sample and justification brought to you by | |
// Isaac Z. Schlueter, aka isaacs | |
// standard style | |
var a = "ape", | |
b = "bat", | |
c = "cat", | |
d = "dog", |
#!/bin/bash -e | |
# Author: gdbtek (Nam Nguyen) | |
# Repo: https://github.com/gdbtek/ubuntu-cookbooks | |
# License: MIT | |
################### | |
# ARRAY UTILITIES # | |
################### | |
function arrayToString() |
// TODO: Clean up thoughts into a nice document. | |
// Thoughts on Universal Data language / description | |
// See: https://martin.kleppmann.com/2012/12/05/schema-evolution-in-avro-protocol-buffers-thrift.html#comment-2534873305 | |
/* Preface: | |
Why do Thrift, Protobuf, and Avro each define their own IDL? | |
I would think that there could be an implementation-independent "master" IDL | |
to standardize the syntax (the semantics depends on the feature set of the implementation). | |
It makes it hard to try out these different libraries when they require rewriting | |
the message schema each time. |
Mocha does not reload modules when running multiple tests. This can lead to some curious errors that are difficult to understand at first, but have to do with modules that have an internal state of their own. If you have a folder with two files, test1.js and test2.js (shown in gist below), you will find you get different test results even though they are identical except in name. The first one fails, but the second succeeds.
So some state from previous tests can "pollute" later tests. This makes it difficult to write unit tests in isolation with Mocha, because suddenly when you put both tests together in the same directoy, mocha's behavior can break the tests.