ordinaryzelig

I'm a fan of MiniTest::Spec. It strikes a nice balance between the simplicity of TestUnit and the readable syntax of RSpec. When I first switched from RSpec to MiniTest::Spec, one thing I was worried I would miss was the ability to add matchers. (A note in terminology: "matchers" in MiniTest::Spec refer to something completely different than "matchers" in RSpec. I won't get into it, but from now on, let's use the proper term: "expectations").

Understanding MiniTest::Expectations

Let's take a look in the code (I'm specifically referring to the gem, not the standard library that's built into Ruby 1.9):

# minitest/spec.rb

module MiniTest::Expectations

josheinstein

// Handle back button issues with Twitter Bootstrap's tab component.
// Based on: http://stackoverflow.com/a/10120221/81769
// It has been changed to avoid the following side effects:
// - Switching tabs was being added to navigation history which is undesirable
//   (Worked around this by using location.replace instead of setting the hash property)
// - Browser scroll position was lost due to fragment navigation
//   (Worked around this by converting #id values to #!id values before navigating.)
$(document).ready(function () {

    if (location.hash.substr(0,2) == "#!") {

eirikb

const req = require.context('./components/', true, /\.(js|vue)$/i);
req.keys().map(key => {
  const name = key.match(/\w+/)[0];
  return Vue.component(name, req(key))
});

rkh

# coding: utf-8
require 'sinatra'
set server: 'thin', connections: []

get '/' do
  halt erb(:login) unless params[:user]
  erb :chat, locals: { user: params[:user].gsub(/\W/, '') }
end

get '/stream', provides: 'text/event-stream' do

chrislkeller

Demo: ajax-handlebars

This repo's location has changed.

rkh

This allows you to use the following video streaming services outside of the US from your Mac without having to use a proxy or VPN, so no big bandwidth issues:

• Hulu / HuluPlus
• CBS
• ABC
• MTV
• theWB
• CW TV
• Crackle
• NBC

NetOpWibby

<script>
  // import
  import { onMount } from "svelte";

  // util
  import { metadata } from "~util";

  // redirect
  onMount(() => {
    // `location.replace` forces a hard refresh in the browser,

wycats

# Just wanted to clarify my points at the meetup last night.
#
# There were two different issues intertwined:
# (1) Whether to use extend or "include as extend"
# (2) When using "include as extend", what is the simplest way to achieve the goal?
#
# My personal opinion is that the answer to (1) is "extend", not "include as extend", but that
# is just my personal opinion. My answer to (2) is a more empirical question.

# Using the "extend" approach. Again, I personally prefer the simplicity of this approach, but

evdama

<script>
import { onMount } from 'svelte';
let html, currentColorScheme = 'light';

onMount(
  () => {
    html = document.getElementsByTagName('html')[0]

    window.matchMedia('(prefers-color-scheme: dark)').addListener(({ matches }) => {
      if (matches) {

jnunemaker

# include this in application controller
module Authentication
  protected
    # Inclusion hook to make #current_user and #signed_in?
    # available as ActionView helper methods.
    def self.included(base)
      base.send :helper_method, :current_user, :signed_in?, :authorized? if base.respond_to? :helper_method
    end
    
    # Returns true or false if the user is signed in.