av1m

"""Utility functions"""

from functools import reduce
from operator import getitem
from typing import Any, Mapping, Union


def getdeep(data: Mapping, map_list: Union[list, str], default: Any = None) -> Any:
    """Iterate nested dictionary|list and can return default value if key not found

tekin

# Stick this in your home directory and point your Global Git config at it by running:
#
#  $ git config --global core.attributesfile ~/.gitattributes
#
# See https://tekin.co.uk/2020/10/better-git-diff-output-for-ruby-python-elixir-and-more for more details

*.c     diff=cpp
*.h     diff=cpp
*.c++   diff=cpp
*.h++   diff=cpp

mohanpedala

Table of Contents

• set -e, -u, -x, -o pipefail
• set -e
• set -x
• set -u
• set -o pipefail
• Setting IFS
• Original Reference

set -e, -u, -x, -o pipefail

jasonnoble

#!/usr/bin/env ruby
#
# Prerequisites:
#   gem install bundler
#   bundle install

dependencies = `bundle show | grep '*' | awk '{print $2, $3}' | sed -e 's/(//' -e 's/)//'`.split("\n")

dependencies.each do |dependency|
  (gem_name, version) = dependency.split

clupprich

begin
  require "bundler/inline"
rescue LoadError => e
  $stderr.puts "Bundler version 1.10 or later is required. Please update your Bundler"
  raise e
end

gemfile(true) do
  source "https://rubygems.org"

mpraglowski

require 'rails_event_store'
require 'aggregate_root'

PaymentAuthorized = Class.new(RailsEventStore::Event)
PaymentSuccessed  = Class.new(RailsEventStore::Event)
PaymentFailed     = Class.new(RailsEventStore::Event)
PaymentCaptured   = Class.new(RailsEventStore::Event)

class Payment
  InvalidOperation = Class.new(StandardError)

mbostock

license: bsd-3-clause

derwiki

Adding an audit log to your Rails app

If you have any sort of administrative interface on your web site, you can easily imagine an intruder gaining access and mucking about. How do you know the extent of the damage? Adding an audit log to your app is one quick solution. An audit log should record a few things:

• controller entry points with parameter values
• permanent information about the user, like user_id
• transient information about the user, like IP and user_agent

Using the Rails framework, this is as simple as adding a before_action to your admin controllers. Here’s a basic version that I’m using in production.

shiroyasha

class Dog 
  attr_writer :name

  def initialize(name)
    @name = name
  end 

  def bark
    puts "patrick"
  end

benhughes

#A brief intro into Stateless functions#

So stateless functions are new in React 0.14 which are quite interesting. They look a bit like this.

const Test = ({name, amount}) => {
  return <div className="test">{name} has £{amount}</div>;
};

ReactDOM.render(<Test name="ben" amount="-2000" />) //  <div className="test">ben has £-200</div>