pedrouid

[
  {
    "name": "Afar",
    "type": "living",
    "scope": "individual",
    "iso-639-3": "aar",
    "iso-639-2B": "aar",
    "iso-639-2T": "aar",
    "iso-639-1": "aa"
  },

rafasashi

array (
  'aa' => 
  array (
    'name' => 'Afar',
    'native' => 'Afaraf',
    'iso_639_1' => 'aa',
    'iso_639_2' => 'aar',
    'iso_639_3' => 'aar',
    'script' => 

dinatih

# config/initializers/activestorage.rb
Rails.application.config.to_prepare do
  # Provides the class-level DSL for declaring that an Active Record model has attached blobs.
  ActiveStorage::Attached::Macros.module_eval do
    def has_one_attached(name, dependent: :purge_later, acl: :private)
      class_eval <<-CODE, __FILE__, __LINE__ + 1
        def #{name}
          @active_storage_attached_#{name} ||= ActiveStorage::Attached::One.new("#{name}", self, dependent: #{dependent == :purge_later ? ":purge_later" : "false"}, acl: "#{acl}")
        end

metasean

These files show one way to make the next.js "with-global-stylesheet" example work with the amazingly awesome Storybook ecosystem.

Specifically, the three files below replace the next.config.js file, in the "with-global-stylesheet" example.

More generically, they demonstrate how to share webpack configuration extensions between next.js and Storybook.

A massive THANK YOU to tmeasday for all his help to get these working!

Envek

# Enables PostgreSQL interval datatype support (as ActiveSupport::Duration) in Ruby on Rails 4.1.
# Based on https://gist.github.com/clarkdave/6529610

require 'active_support/duration'

# add a native DB type of :interval
ActiveRecord::ConnectionAdapters::PostgreSQLAdapter::NATIVE_DATABASE_TYPES[:interval] = { name: 'interval' }

# add the interval type to the simplified_type list. because this method is a case statement
# we can't inject anything into it, so we create an alias around it so calls to it will call

domenic

module.exports = and ES6 Module Interop in Node.js

The question: how can we use ES6 modules in Node.js, where modules-as-functions is very common? That is, given a future in which V8 supports ES6 modules:

• How can authors of function-modules convert to ES6 export syntax, without breaking consumers that do require("function-module")()?
• How can consumers of function-modules use ES6 import syntax, while not demanding that the module author rewrites his code to ES6 export?

@wycats showed me a solution. It involves hooking into the loader API to do some rewriting, and using a distinguished name for the single export.

This is me eating crow for lots of false statements I've made all over Twitter today. Here it goes.

redinger

Setting up Emacs daemon on OS X

Tired of waiting for emacs to start on OS X? This step by step guide will teach you how to install the latest version of emacs and configure it to start in the background (daemon mode) and use emacsclient as your main editor.

Install Cocoa Emacs

Download the latest pretest version of [Emacs for Mac OS X]: http://emacsformacosx.com/builds