nodefortytwo

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$id": "http://dazn.com/manifest.schema.json",
  "title": "dazn-manifest",
  "type": "object",
  "additionalProperties": false,
  "description": "A YAML file which describes the contents of a code repository in a machine readable format.",
  "properties": {
    "dazn-manifest": {
      "title": "version",

nodefortytwo

RFC 002 - dazn-manifest

Current Version: 3.3.0

Contributors:

Index:

• RFC 002 - dazn-manifest

petrokoriakin

# config/initializers/grape.rb

module AppstackGrapeEndpointSetup
    extend ActiveSupport::Concern

    module ClassMethods
      include Rails.application.routes.url_helpers
      def default_url_options
        {host: ::Rails.application.config.action_mailer.default_url_options[:host]}
      end

jashkenas

// Here is a proposal for minimalist JavaScript classes, humbly offered.

// There are (at least) two different directions in which classes can be steered.
// If we go for a wholly new semantics and implementation, then fancier classical
// inheritance can be supported with parallel prototype chains for true inheritance
// of properties at both the class and instance level.

// If however, we keep current JavaScript prototype semantics, and add a form that
// can desugar to ES3, things must necessarily stay simpler. This is the direction
// I'm assuming here.