trek

// get a Casper object.
// See http://casperjs.org/
var casper = require('casper').create();

// this will be evaluated inside the context of the window.
// See http://casperjs.org/api.html#casper.evaluate for notes on
// the difference between casper's running environment and the 
// DOM environment of the loaded page.
function testReporter(){
  // casper is webkit, so we have good DOM methods. You're

bradwilson

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp1.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.0.0-preview-20170106-08" />
    <PackageReference Include="xunit" Version="2.2.0-beta5-build3474" />

heejune

import sys
import asyncio
import telepot
from telepot.aio.delegate import per_chat_id, create_open

import picam


"""
$ python3.5 countera.py <token>

alicial

// Mocked Service
angular.module('mock.users', []).
    factory('UserService', function($q) {
        var userService = {};

        userService.get = function() {
            return {
                id: 8888,
                name: "test user"
            }

gulpfile.js

var gulp        = require("gulp");
var sass        = require("gulp-sass");
var autoprefix  = require("gulp-autoprefixer");
var filter      = require('gulp-filter');
var browserSync = require('browser-sync');
var reload      = browserSync.reload;

/**
 * Start BrowserSync
 */

mathiasbynens

// Original code from http://www.blog.highub.com/mobile-2/a-fix-for-iphone-viewport-scale-bug/

var metas = document.getElementsByTagName('meta');
var i;
if (navigator.userAgent.match(/iPhone/i)) {
	for (i=0; i<metas.length; i++) {
		if (metas[i].name == "viewport") {
			metas[i].content = "width=device-width, minimum-scale=1.0, maximum-scale=1.0";
		}
	}

addyosmani

#Four Ways To Do Pub/Sub With jQuery and jQuery UI (in the future)

Between jQuery 1.7 and some of work going into future versions of jQuery UI, there are a ton of hot new ways for you to get your publish/subscribe on. Here are just four of them, three of which are new.

(PS: If you're unfamiliar with pub/sub, read the guide to it that Julian Aubourg and I wrote here http://msdn.microsoft.com/en-us/scriptjunkie/hh201955.aspx)

##Option 1: Using jQuery 1.7's $.Callbacks() feature:

$.Callbacks are a multi-purpose callbacks list object which can be used as a base layer to build new functionality including simple publish/subscribe systems. We haven't yet released the API documentation for this feature just yet, but for more information on it (including lots of examples), see my post on $.Callbacks() here:

topdown

<?php 
/* Use an autoloader on include to load this but do not instance it 
 * OPTION ONE (autoloaded or included)
 * Name the class like this
 * class wpdb_docs extends wpdb {}
 *
 * /** @var $tag wpdb_docs */
 * $tag_urls = get_tag_link($tag->term_id);
 *
 * OPTION TWO and probably the best

klihelp

<?php
/**
 * WP-API modify post response fields
 * 
 */

/**
 * Posts per page
 */
function kli_wp_api_query_post_per_page( $query ){

JoshuaKGoldberg

👉 This has since been posted to DefinitelyTyped's GitHub Discussions: DefinitelyTyped/DefinitelyTyped#65993 👈

Context

👋 Hi all! I've been working with the TypeScript team on overhauling DefinitelyTyped's usage of formatting and linting tools. Alongside the effort to finally migrate from TSLint to ESLint (https://typescript-eslint.io/linting/troubleshooting/tslint -> microsoft/DefinitelyTyped-tools#648), we'd like to align with how much of the industry & many linter maintainers recommend using a formatter vs. a linter (myself included).

This is a surfacing of a plan we've formulated that we think will get DefinitelyTyped onto using a proper formatter for formatting. I'd very much like to see the community's reaction: does this seem reasonable to you? What edge cases are we missing? Will this offend your sensibilities as a program